public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Vivek Natarajan <Vivek.Natarajan@atheros.com>,
	Easwar Krishnan <Easwar.Krishnan@atheros.com>,
	Nataraj Sadasivam <Nataraj.Sadasivam@atheros.com>,
	Kathir Ganapthy <Kathir.Ganapthy@atheros.com>,
	Ponmudi Ramachandran <Ponmudi.Ramachandran@atheros.com>,
	Senthilkumar Balasubramanian
	<Senthilkumar.Balasubramanian@atheros.com>
Subject: Re: [RFT v9] rfkill: rewrite
Date: Thu, 14 May 2009 12:00:52 +0200	[thread overview]
Message-ID: <1242295252.500.0.camel@johannes.local> (raw)
In-Reply-To: <9b2b86520905140258t7c169ec7k254deea5d01b6254@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Thu, 2009-05-14 at 10:58 +0100, Alan Jenkins wrote:

> > Very good, thank you! That means I don't have to fix anything in
> > rfkill :)
> 
> Yep, seems so.  I'm now able to test the rfkill functionality and it
> all seems fine.  The new resume code successfully fixes the
> hibernation corner-case I brought up.  So I'm happy and you can add my
> 
> Tested-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>

Thanks.

> You should probably drop my Signed-off-by though, seeing as it no
> longer includes the eeepc-laptop resume handler I wrote.

Ok.

> Oh, and don't forget the "whitespace error" flagged by git-apply.
> scripts/checkpatch.pl will flag it up as well.   Checkpatch also says
> you shouldn't initialize "rfkill_no = 0" because it's a static (and
> therefore will default to zero in the absence of an initializer).

Good plan, I'll fix those, thanks.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-05-14 10:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  8:31 [RFT v9] rfkill: rewrite Johannes Berg
2009-05-12 14:09 ` Alan Jenkins
2009-05-13 10:49   ` Johannes Berg
2009-05-13 14:36     ` Alan Jenkins
2009-05-13 14:38       ` Johannes Berg
2009-05-13 21:48         ` Luis R. Rodriguez
2009-05-13 21:45   ` Luis R. Rodriguez
2009-05-14  9:02     ` Alan Jenkins
2009-05-14  9:08       ` Johannes Berg
2009-05-14  9:58         ` Alan Jenkins
2009-05-14 10:00           ` Johannes Berg [this message]
2009-05-14  4:34   ` Luis R. Rodriguez
2009-05-14  8:24     ` Alan Jenkins
2009-05-12 17:26 ` Will Keaney
2009-05-12 17:52   ` Johannes Berg
2009-05-12 17:59   ` Dan Williams
2009-05-12 18:04     ` Johannes Berg
2009-05-12 18:09       ` Will Keaney
2009-05-12 18:13         ` Johannes Berg
2009-05-13 21:40       ` Henrique de Moraes Holschuh
2009-05-13 22:19         ` Johannes Berg
2009-05-15  1:27           ` Henrique de Moraes Holschuh
2009-05-15  8:23             ` Johannes Berg
2009-05-18 11:00         ` Henrique de Moraes Holschuh
2009-05-19 12:12           ` Johannes Berg
2009-05-19 18:24             ` Henrique de Moraes Holschuh

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=1242295252.500.0.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Easwar.Krishnan@atheros.com \
    --cc=Kathir.Ganapthy@atheros.com \
    --cc=Nataraj.Sadasivam@atheros.com \
    --cc=Ponmudi.Ramachandran@atheros.com \
    --cc=Senthilkumar.Balasubramanian@atheros.com \
    --cc=Vivek.Natarajan@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=sourcejedi.lkml@googlemail.com \
    /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