From: Ben Hutchings <ben@decadent.org.uk>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: dwmw2@infradead.org, ath6kl-devel@qualcomm.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/2] linux-firmware: ath6k update 20120410
Date: Mon, 16 Apr 2012 15:15:57 +0100 [thread overview]
Message-ID: <1334585757.3209.125.camel@deadeye> (raw)
In-Reply-To: <1334541087.3209.39.camel@deadeye>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Mon, 2012-04-16 at 02:51 +0100, Ben Hutchings wrote:
> On Tue, 2012-04-10 at 15:18 +0300, Kalle Valo wrote:
> > (Resending as my --cc had a space and stgit didn't send this to the mailing
> > lists.)
> >
> > Hi Ben,
> >
> > here's a firmware update for ath6k. We update the AR6003 hw2.1.1 to the
> > latest in our 3.2.0 branch and add a new firmware for AR6004.
> >
> > This is the first time I'm sending patches for linux-firmware so please
> > let me know if there are any errors.
>
> I've applied these. However, in future please only add File: lines to
> WHENCE for regular files. I've now removed all such lines from the
> listings for ath6kl.
What I meant to say is that I removed File: lines that referred to
directories.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-04-16 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 12:18 [PATCH 0/2] linux-firmware: ath6k update 20120410 Kalle Valo
2012-04-10 12:18 ` [PATCH 1/2] linux-firmware: ath6k: add AR6003 hw2.1.1 firmware version 3.2.0.144 Kalle Valo
2012-04-10 12:18 ` [PATCH 2/2] linux-firmware: ath6k: add firmware for AR6004 hw1.2 Kalle Valo
2012-04-16 1:51 ` [PATCH 0/2] linux-firmware: ath6k update 20120410 Ben Hutchings
2012-04-16 6:03 ` Kalle Valo
2012-04-16 14:15 ` Ben Hutchings [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=1334585757.3209.125.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=ath6kl-devel@qualcomm.com \
--cc=dwmw2@infradead.org \
--cc=kvalo@qca.qualcomm.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.