linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: Joe Perches <joe@perches.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request:  staging: ath6kl: linux kernel style cleanups
Date: Wed, 15 Dec 2010 13:14:33 -0800	[thread overview]
Message-ID: <20101215211433.GA932@kroah.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F98406D966A13@SC1EXMB-MBCL.global.atheros.com>

On Wed, Dec 15, 2010 at 12:47:42PM -0800, Vipin Mehta wrote:
> 
> -----Original Message-----
> From: Joe Perches [mailto:joe@perches.com] 
> Sent: Wednesday, December 15, 2010 12:39 AM
> To: Vipin Mehta
> Cc: Luis R. Rodriguez; devel@driverdev.osuosl.org; linux-wireless
> Subject: pull request: staging: ath6kl: linux kernel style cleanups
> 
> A too-large-to-post (~2MB) changeset to ath6kl, sent separately to Vipin and Luis.
> 
> Mostly done mechanically.  Compile tested only.
> 
> The following changes since commit e3d7018ee7b5205a80b1011f5a86432de40ce74a:
> 
>   Add linux-next specific files for 20101215 (2010-12-15 14:37:00 +1100)
> 
> are available in the git repository at:
>   git://repo.or.cz/linux-2.6/trivial-mods.git 20101215-ath6kl
> 
> LGTM.
> 
> Greg,
> Can you kindly pull in these changes into ath6kl?

Please send them to me in patch form so that I can apply them.  You need
to provide your ack on them as well.

> Also, would you know
> what kind of changes can be migrated to Linus's 2.6.37 kernel. Is it
> only limited to bug fixes or code cleanup can also be a part of it?

At this point in the release cycle, what do you think?

If you are unsure of how the release cycle works, please read
Documentation/development_process/

thanks,

greg k-h

      reply	other threads:[~2010-12-15 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimfPFeLy5sfDDS5fXiK8X8UT2x8dhzZ+_FEjrTo@mail.gmail.com>
     [not found] ` <1292363199.26726.34.camel@Joe-Laptop>
     [not found]   ` <AANLkTikD440S8AWcOdib7BfTR5a7CaTuYjkysi43oaQZ@mail.gmail.com>
     [not found]     ` <35B17FE5076C7040809188FBE7913F98406D8912FE@SC1EXMB-MBCL.global.atheros.com>
2010-12-15  8:39       ` pull request: staging: ath6kl: linux kernel style cleanups Joe Perches
2010-12-15  8:59         ` Joe Perches
2010-12-15 20:47         ` Vipin Mehta
2010-12-15 21:14           ` 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=20101215211433.GA932@kroah.com \
    --to=greg@kroah.com \
    --cc=Vipin.Mehta@Atheros.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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;
as well as URLs for NNTP newsgroup(s).