From: Dan Williams <dcbw@redhat.com>
To: Marco Chiappero <marco@absence.it>
Cc: netdev@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: rfkill-input to be removed
Date: Thu, 21 Apr 2011 10:51:35 -0500 [thread overview]
Message-ID: <1303401097.16512.17.camel@dcbw.foobar.com> (raw)
In-Reply-To: <4DB03586.3040702@absence.it>
On Thu, 2011-04-21 at 15:47 +0200, Marco Chiappero wrote:
> Il 21/04/2011 10:28, Marco Chiappero ha scritto:
> > Please remove that code as soon as possible, rfkill input events should
> > be handled by user space tools.
>
> About this topic, I've created a patch right now, you can find it here:
> http://www.absence.it/vaio-acpi/source/patches/rfkill-input.patch
> Does it look fine?
You'll want to follow the patch submission guidelines:
http://linux.yyz.us/patch-format.html
before people will look at the patch, because many of the people who
would look at it are quite busy. That means:
1) use a subject like "[PATCH] rfkill-input: remove deprecated module"
2) Add your Signed-off-by: Your Name <your email>
3) paste your patch *inline*, not as an attachment, and make *sure* to
use the "preformat" or whatever option when you do, so that your mailer
doesn't wrap long lines
Dan
> Moreover, using checkpatch.pl I've found 3 coding style errors, I'm
> attaching a patch to fix them (apply this one first).
>
> And just one last thing: as there is no configuration option inside the
> menu, shouldn't we change the "menuconfig RFKILL" line to "config
> RFKILL" inside net/rfkill/Kconfig?
next prev parent reply other threads:[~2011-04-21 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 8:28 rfkill-input to be removed Marco Chiappero
2011-04-21 13:47 ` Marco Chiappero
2011-04-21 15:51 ` Dan Williams [this message]
2011-04-21 16:22 ` Johannes Berg
2011-04-21 16:45 ` Marco Chiappero
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=1303401097.16512.17.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=marco@absence.it \
--cc=netdev@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