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 11:48:40 -0800 [thread overview]
Message-ID: <20110121194840.GA18603@vmehta-desktop> (raw)
In-Reply-To: <20110121193830.GA17789@kroah.com>
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.
>
> So, care to make up a git tree that I could pull these from? Or at the
> least, rebase them so that I can apply them?
There is git tree here which was originally pulled from the staging-2.6 tree and has all these changes.
http://git.kernel.org/?p=linux/kernel/git/vmehta/ath6kl.git;a=shortlog;h=refs/heads/ath6kl-cleanup
Tree: git://git.kernel.org/pub/scm/linux/kernel/git/vmehta/ath6kl.git
Head: ath6kl-cleanup
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2011-01-21 19:49 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 [this message]
2011-01-21 19:55 ` Greg KH
2011-01-21 20:09 ` Vipin Mehta
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=20110121194840.GA18603@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox