From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch 2/2] staging: ath6kl: buffer overflow in SEND_FRAME ioctl
Date: Wed, 23 Feb 2011 18:54:19 +0000 [thread overview]
Message-ID: <20110223185419.GA686@kroah.com> (raw)
In-Reply-To: <20110220124953.GB1898@bicker>
On Wed, Feb 23, 2011 at 10:40:50AM -0800, Luis R. Rodriguez wrote:
> On Sun, Feb 20, 2011 at 7:18 AM, Vipin Mehta <vmehta@atheros.com> wrote:
>
> > Acked-by: Vipin Mehta <vipin.mehta@atheros.com>
>
> Greg, Joe is not sure if these patches will be applied as-is and his
> cleanup depends on code being static, I think they would be there is a
> chance you might muck them a bit and this would break any cleanup
> work. Will these patches be merged as-is, can Joe for example git am
> these into his tree as-is and work off of the assumption that they
> will reflect the top of staging-next + these patches?
I already answered Joe about this yesterday, was that response somehow
not sufficient?
thanks,
greg "tired of repeating myself" k-h
prev parent reply other threads:[~2011-02-23 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 12:49 [patch 2/2] staging: ath6kl: buffer overflow in SEND_FRAME ioctl Dan Carpenter
2011-02-20 15:18 ` [patch 2/2] staging: ath6kl: buffer overflow in SEND_FRAME Vipin Mehta
2011-02-23 18:40 ` [patch 2/2] staging: ath6kl: buffer overflow in SEND_FRAME ioctl Luis R. Rodriguez
2011-02-23 18:54 ` 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=20110223185419.GA686@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox