From: Dan Carpenter <error27@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Fix sparse message rtl8192u
Date: Sun, 28 Nov 2010 21:19:55 +0000 [thread overview]
Message-ID: <20101128211955.GD30799@bicker> (raw)
In-Reply-To: <1290634903.4ced8697b0603@webmail.aliceadsl.fr>
On Sat, Nov 27, 2010 at 11:37:48PM +0100, David Chosrova wrote:
> Hello,
>
> In this patch I have removed the #ifdef ENABLE_DOT11D.
>
Cool man. Looks good.
There are several places where ENABLE_DOT11D is still there in the
comments. Can do a: grep ENABLE_DOT11D drivers/staging/rtl8192u/ -R
and remove all those?
Then add an:
Acked-by: Dan Carpenter <error27@gmail.com>
When people apply patches they try to automate the process. They
have scripts that automatically take an email and creates a kernel
patch. So choose a good subject and write a patch description.
I would normally write this:
Subject: [patch] Staging: rtl8192u: remove dead code to disable dot11d
This patch removes all the ENABLE_DOT11D ifdefs. It's always enabled
for this driver. DOT11D has to do with regulatory domains.
What prompted this patch was a warning message in Sparse:
drivers/staging/rtl8192u/r8192U_core.c:247:1: warning: "eqMacAddr"
redefined in file included from drivers/staging/rtl8192u/:81:81:
drivers/staging/rtl8192u/dot11d.h:35:1: warning: this is the location
of the previous definition
Now there are no ifdefs around dot11d.h it made no sense to have this
second definition, so I removed that macro as well.
---
Edit that however you want. That's just an idea.
Don't put the "Hello etc" into the message because Greg will have to
strip those bits out of the patch description by hand.
After the Signed-off-by: line put three dashes "---". Things below that
line get stripped out of the patch description. That's where you can
put the "Compile tested." or "Feedback requested" stuff if you want.
Send your email to: gregkh@suse.de
CC these addresses: devel@driverdev.osuosl.org, error27@gmail.com,
andreamrl@tiscali.it, linux-wireless@vger.kernel.org,
kernel-janitors@vger.kernel.org
regards,
dan carpenter
next prev parent reply other threads:[~2010-11-28 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 21:41 [PATCH] Fix sparse message rtl8192u david.chosrova
2010-11-25 5:36 ` Dan Carpenter
2010-11-25 9:39 ` david chosrova
2010-11-25 10:04 ` Dan Carpenter
2010-11-27 22:37 ` David Chosrova
2010-11-28 21:19 ` Dan Carpenter [this message]
2010-11-30 15:35 ` [PATCH] Staging: rtl8192u: remove dead code to disable dot11d David Chosrova
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=20101128211955.GD30799@bicker \
--to=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
/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