From: "John W. Linville" <linville@tuxdriver•com>
To: Dmytro Milinevskyy <milinevskyy@gmail•com>
Cc: Jiri Slaby <jirislaby@gmail•com>,
Nick Kossifidis <mickflemm@gmail•com>,
"Luis R. Rodriguez" <lrodriguez@atheros•com>,
Bob Copeland <me@bobcopeland•com>,
GeunSik Lim <geunsik.lim@samsung•com>,
Greg Kroah-Hartman <gregkh@suse•de>,
Lukas Turek <8an@praha12•net>, Mark Hindley <mark@hindley•org.uk>,
Johannes Berg <johannes@sipsolutions•net>,
Jiri Kosina <jkosina@suse•cz>, Kalle Valo <kalle.valo@iki•fi>,
Keng-Yu Lin <keng-yu.lin@canonical•com>,
Luca Verdesca <magooz@salug•it>,
Shahar Or <shahar@shahar-or•co.il>,
linux-wireless@vger•kernel.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH] [ath5k][leds] Ability to disable leds support. If leds support enabled do not force mac802.11 leds layer selection.
Date: Fri, 4 Jun 2010 10:09:19 -0400 [thread overview]
Message-ID: <20100604140919.GA2492@tuxdriver.com> (raw)
In-Reply-To: <4c0804e2.0c3ddf0a.2771.10f7@mx.google.com>
On Thu, Jun 03, 2010 at 10:39:30PM +0300, Dmytro Milinevskyy wrote:
> Hi!
>
> Here is the patch to disable ath5k leds support on build stage.
> However if the leds support was enabled do not force selection of 802.11 leds layer.
> Depency on LEDS_CLASS is kept.
>
> Suggestion given by Pavel Roskin and Bob Copeland applied.
>
> Regards,
>
> --Dima
Needs at least a Signed-off-by line, and preferrably a changelog that
explains what the patch is doing and (especially) why it is necessary.
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:[~2010-06-04 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 19:39 [PATCH] [ath5k][leds] Ability to disable leds support. If leds support enabled do not force mac802.11 leds layer selection Dmytro Milinevskyy
2010-06-04 14:09 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-09 7:31 Dmytro Milinevskyy
2010-06-09 13:58 ` [ath5k-devel] " Bob Copeland
2010-06-09 14:43 ` Dmytro Milinevskyy
[not found] ` <AANLkTimXqdkQxv_Y1JaleTTWNsDIQHQaPn8HR7efOupb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-11 20:09 ` Johannes Berg
2010-06-11 20:26 ` [ath5k-devel] " Dmytro Milinevskyy
[not found] ` <AANLkTim90VBfWjp2YPYeYN6ImjIyZzcJ_XnpT5cdgCt4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-11 20:29 ` Johannes Berg
2010-06-04 13:43 Dmytro Milinevskyy
2010-06-04 16:22 ` Pavel Roskin
2010-06-07 7:39 ` Dmytro Milinevskyy
2010-04-07 18:58 Dmytro Milinevskyy
2010-06-01 20:34 ` Bob Copeland
2010-06-01 23:01 ` Dmytro Milinevskyy
2010-04-07 18:58 Dmytro Milinevskyy
2010-04-07 18:58 Dmytro Milinevskyy
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=20100604140919.GA2492@tuxdriver.com \
--to=linville@tuxdriver$(echo .)com \
--cc=8an@praha12$(echo .)net \
--cc=geunsik.lim@samsung$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=jirislaby@gmail$(echo .)com \
--cc=jkosina@suse$(echo .)cz \
--cc=johannes@sipsolutions$(echo .)net \
--cc=kalle.valo@iki$(echo .)fi \
--cc=keng-yu.lin@canonical$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=lrodriguez@atheros$(echo .)com \
--cc=magooz@salug$(echo .)it \
--cc=mark@hindley$(echo .)org.uk \
--cc=me@bobcopeland$(echo .)com \
--cc=mickflemm@gmail$(echo .)com \
--cc=milinevskyy@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shahar@shahar-or$(echo .)co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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