From: Greg KH <greg@kroah.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: G?bor Stefanik <netrolller.3d@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH 0/1] ath6kl: add ath6kl driver for AR6003 chip
Date: Thu, 2 Sep 2010 11:47:20 -0700 [thread overview]
Message-ID: <20100902184720.GA3330@kroah.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F234795C2@SC1EXMB-MBCL.global.atheros.com>
On Thu, Sep 02, 2010 at 10:54:03AM -0700, Vipin Mehta wrote:
> Greg,
> Besides the size of the original patch, I was not very confident of
> the exchange server through which my emails go out. The patch may get
> mangled in which case you wont be able to apply it. I am working on it
> to make sure that I have a reliable way to send the patches out. Until
> then, downloading the patch from the location that I specified may be
> a better option.
>
> http://www.kernel.org/~vmehta/0001-staging-add-ath6kl-driver-for-AR6003-chip.patch.gz
>
> If the link above does not work out, then I'll send the patch to you
> via an email (its about 5 MB uncompressed). Let me know.
Ok, I've taken the above patch and applied it to the staging-next tree
now.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-02 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 22:51 [PATCH 0/1] ath6kl: add ath6kl driver for AR6003 chip Vipin Mehta
2010-09-02 1:35 ` Greg KH
2010-09-02 2:29 ` Gábor Stefanik
2010-09-02 3:25 ` Greg KH
2010-09-02 17:54 ` Vipin Mehta
2010-09-02 18:47 ` Greg KH [this message]
2010-09-02 6:57 ` Peter Korsgaard
2010-09-02 9:55 ` Michael Trimarchi
2010-09-02 10:38 ` Timo Juhani Lindfors
2010-09-02 18:12 ` Vipin Mehta
2010-09-02 20:52 ` Timo Juhani Lindfors
2010-09-02 18:04 ` Vipin Mehta
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=20100902184720.GA3330@kroah.com \
--to=greg@kroah.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Vipin.Mehta@Atheros.com \
--cc=devel@linuxdriverproject.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@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).