From: "John W. Linville" <linville@tuxdriver.com>
To: Janakiram Sistla <janakiram.sistla@gmail.com>
Cc: marcel@holtmann.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] Adding radio type FM
Date: Tue, 17 Nov 2009 13:31:50 -0500 [thread overview]
Message-ID: <20091117183150.GA31701@tuxdriver.com> (raw)
In-Reply-To: <1258480113-20841-1-git-send-email-janakiram.sistla@gmail.com>
On Tue, Nov 17, 2009 at 11:18:33PM +0530, Janakiram Sistla wrote:
> From: Janakiram Sistla <janakiram.sistla@gmail.com>
>
> Adding radio type FM in RFKILL_TYPE_.FM belongs to
> same class of with both TX/RX capability.
>
> Signed-off-by: Janakiram Sistla <janakiram.sistla@gmail.com>
> ---
> include/linux/rfkill.h | 1 +
> net/rfkill/core.c | 2 ++
> 2 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
> index 3392c59..03f5598 100644
> --- a/include/linux/rfkill.h
> +++ b/include/linux/rfkill.h
> @@ -45,6 +45,7 @@ enum rfkill_type {
> RFKILL_TYPE_WIMAX,
> RFKILL_TYPE_WWAN,
> RFKILL_TYPE_GPS,
> + RFKILL_TYPE_FM,
> NUM_RFKILL_TYPES,
> };
>
> diff --git a/net/rfkill/core.c b/net/rfkill/core.c
> index ba2efb9..61b716e 100644
> --- a/net/rfkill/core.c
> +++ b/net/rfkill/core.c
> @@ -590,6 +590,8 @@ static const char *rfkill_get_type_str(enum rfkill_type type)
> return "wimax";
> case RFKILL_TYPE_WWAN:
> return "wwan";
> + case RFKILL_TYPE_FM:
> + return "fm";
> case RFKILL_TYPE_GPS:
> return "gps";
> default:
My personal taste would dictate that you add the case statement
in the same place that you added the enum. Depending on which
order you choose, you may need to change the BUILD_BUG_ON on line
601 of net/rfkill/core.c. (Not sure how you managed to build w/
this patch...)
Also, when you add the enum you need to add the corresponding kerneldoc
(i.e. an @RFKILL_TYPE_FM comment) just above it.
Finally, please add "rfkill: " to the beginning of the subject line
when you resubmit your patch.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-11-17 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 17:48 [PATCH 1/1] Adding radio type FM Janakiram Sistla
2009-11-17 18:31 ` John W. Linville [this message]
2009-11-17 18:47 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2009-11-13 3:09 [patch 0/1] " Janakiram Sistla
2009-11-13 3:22 ` Marcel Holtmann
2009-11-14 13:19 ` Janakiram Sistla
2009-11-14 16:34 ` Marcel Holtmann
2009-11-14 17:37 ` Janakiram Sistla
2009-11-14 18:05 ` Marcel Holtmann
2009-11-16 2:36 ` [PATCH 1/1] " Janakiram Sistla
2009-11-16 2:43 ` Marcel Holtmann
2009-11-16 4:25 ` Janakiram Sistla
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=20091117183150.GA31701@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=janakiram.sistla@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).