From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] wpa_supplicant: add support for writing debug log to a file
Date: Thu, 15 Aug 2013 08:54:43 +0000 [thread overview]
Message-ID: <embeba4dd6-b8e2-42e7-a50a-1998bed35519@nb-mak> (raw)
In-Reply-To: <520C8C52.1090803@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
>Please indent with one Tab here. Maybe your mailer converted the tab to
>a space.
The patch in the attachment contains tabs, but my mailer converted them.
Can you recommend a GUI mailer which supports tabs in plain-text mails ?
>Do you have some changes in the .make file, too?
No, the .make file copies the config variables automatically using grep
& sed.
Best regards,
Matthias
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 619 bytes --]
Signed-off-by: Matthias Klein <matthias.klein@optimeas.de>
---
rules/wpa_supplicant.in | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/rules/wpa_supplicant.in b/rules/wpa_supplicant.in
index 733a2b5..62b9b08 100644
--- a/rules/wpa_supplicant.in
+++ b/rules/wpa_supplicant.in
@@ -127,4 +127,10 @@ config WPA_SUPPLICANT_INSTALL_CLI
it's not necessary to have wpa_cli in the final (non-development)
version of an Embedded System.
+config WPA_SUPPLICANT_DEBUG_FILE
+ bool
+ prompt "log file support"
+ help
+ Add support for writing debug log to a file
+
endif
--
1.7.10.4
[-- Attachment #3: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-08-15 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 8:00 Matthias Klein
2013-08-15 8:07 ` Marc Kleine-Budde
2013-08-15 8:54 ` Matthias Klein [this message]
2013-08-15 9:13 ` Marc Kleine-Budde
2013-08-15 9:18 ` Marc Kleine-Budde
2013-08-15 9:58 ` Bernhard Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=embeba4dd6-b8e2-42e7-a50a-1998bed35519@nb-mak \
--to=matthias.klein@optimeas.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox