From: Vipin Mehta <vmehta@atheros.com>
To: Greg KH <greg@kroah.com>
Cc: Vipin Mehta <Vipin.Mehta@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"joe@perches.com" <joe@perches.com>
Subject: Re: [PATCH 00/83] staging: ath6kl: Style cleanup
Date: Fri, 21 Jan 2011 12:09:07 -0800 [thread overview]
Message-ID: <20110121200907.GA18651@vmehta-desktop> (raw)
In-Reply-To: <20110121195509.GB18700@kroah.com>
On Fri, Jan 21, 2011 at 11:55:09AM -0800, Greg KH wrote:
> On Fri, Jan 21, 2011 at 11:48:40AM -0800, Vipin Mehta wrote:
> > On Fri, Jan 21, 2011 at 11:38:30AM -0800, Greg KH wrote:
> > > On Fri, Jan 21, 2011 at 11:23:18AM -0800, Vipin Mehta wrote:
> > > > The following set of patches fixes the driver's coding style in
> > > > accordance with the Linux kernel coding style. The patches ended
> > > > being huge so putting them up on a shared location where they can
> > > > be retrieved using wget.
> > > >
> > > > http://userweb.kernel.org/~vmehta/ath6kl-cleanup.tar.bz2
> > >
> > > Interesting, however the very first patch fails to apply :(
> >
> > I generated the patches after rebasing my tree to the
> > remotes/origin/staging-linus in the staging-2.6 tree. I tested it
> > again just a whilw back and the patches do apply.
>
> These patches are NOT for staging-linus as they are not to go to him
> until the .39 merge window is open, right? Please rebase them on the
> staging-next tree.
>
The only difference in ath6kl between the staging-linus and staging-next
is the following patch that was applied yesterday in the staging-linus
branch:
http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=commit;h=64911e4b133ff633563d6dd2b021fa1ca0608992
The reason I used staging-linus is because I wanted to apply these
patches on top of the above patch which we will have to do eventually.
We will have to go through the pain later which I already went through
yesterday while redoing these patches on top of the above one. Is it
possible for you to apply the commit
64911e4b133ff633563d6dd2b021fa1ca0608992
before applying this series?
Regards,
Vipin
next prev parent reply other threads:[~2011-01-21 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:23 [PATCH 00/83] staging: ath6kl: Style cleanup Vipin Mehta
2011-01-21 19:38 ` Greg KH
2011-01-21 19:43 ` Joe Perches
2011-01-21 19:48 ` Vipin Mehta
2011-01-21 19:55 ` Greg KH
2011-01-21 20:09 ` Vipin Mehta [this message]
2011-01-21 21:16 ` Greg KH
2011-01-23 0:24 ` Joe Perches
2011-01-23 9:32 ` Greg KH
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=20110121200907.GA18651@vmehta-desktop \
--to=vmehta@atheros.com \
--cc=Vipin.Mehta@Atheros.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-wireless@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.