From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/2] staging: ath6kl: cleanup in SEND_FRAME ioctl
Date: Tue, 22 Feb 2011 17:36:27 +0000 [thread overview]
Message-ID: <20110222173627.GA6764@kroah.com> (raw)
In-Reply-To: <20110220124832.GA1898@bicker>
On Tue, Feb 22, 2011 at 08:42:09AM -0800, Joe Perches wrote:
> On Sun, 2011-02-20 at 21:04 -0800, Luis R. Rodriguez wrote:
> > On Sun, Feb 20, 2011 at 9:02 PM, Greg KH <greg@kroah.com> wrote:
> > > On Sun, Feb 20, 2011 at 08:45:44PM -0800, Luis R. Rodriguez wrote:
> > >> On Sun, Feb 20, 2011 at 8:14 PM, Greg KH <greg@kroah.com> wrote:
> > >> > On Sun, Feb 20, 2011 at 08:00:38PM -0800, Luis R. Rodriguez wrote:
> > >> >> On Sun, Feb 20, 2011 at 7:18 AM, Vipin Mehta <vmehta@atheros.com> wrote:
> > >> >> > On Sun, Feb 20, 2011 at 04:49:08AM -0800, Dan Carpenter wrote:
> > >> >> >> The original code was written in a funny way where every statement was
> > >> >> >> part of else if blocks. I broke them up into separate statements by
> > >> >> >> adding breaks on failure conditions.
> > >> >> >> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> Greg, can I find out soonish please if you are going to
> apply these patches?
They were sent on Sunday, yesterday was a holiday here, so please give
me a chance to catch up...
> If not, I have patches to send.
> If so, I'll wait until you apply them
> and redo them.
Yes, it looks like I will take these as Vipin acked them.
thanks,
greg k-h
prev parent reply other threads:[~2011-02-22 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 12:49 [patch 1/2] staging: ath6kl: cleanup in SEND_FRAME ioctl Dan Carpenter
2011-02-20 15:18 ` Vipin Mehta
2011-02-21 4:00 ` Luis R. Rodriguez
2011-02-21 4:14 ` Greg KH
2011-02-21 4:45 ` Luis R. Rodriguez
2011-02-21 5:02 ` Greg KH
2011-02-21 5:04 ` Luis R. Rodriguez
2011-02-22 16:42 ` Joe Perches
2011-02-22 17:36 ` Greg KH [this message]
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=20110222173627.GA6764@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.