From: "John W. Linville" <linville@tuxdriver.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/3] iwlwifi driver updates 02/10/2009
Date: Wed, 11 Feb 2009 11:25:50 -0500 [thread overview]
Message-ID: <20090211162549.GA5082@tuxdriver.com> (raw)
In-Reply-To: <1234368987.23593.35.camel@rc-desk>
On Wed, Feb 11, 2009 at 08:16:27AM -0800, reinette chatre wrote:
> On Tue, 2009-02-10 at 15:19 -0800, Chatre, Reinette wrote:
> > Two cleanups and a fix to configure 5000 series FAT channels correctly.
> >
> > [PATCH 1/3] iwlwifi: use pci registers defined in pci_regs.h
> > [PATCH 2/3] iwlwifi: drop PCIe workaround applicable for development boards
> > [PATCH 3/3] iwlwifi: fix FAT channel config for 5000 series
>
> John,
>
> Two of these patches have a duplicate "From:" line that will cause
> git-am to include this information in the commit message.
>
> Should I resend?
>
> Reinette
I've fixed that already, thanks. :-)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-02-11 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 23:19 [PATCH 0/3] iwlwifi driver updates 02/10/2009 Reinette Chatre
2009-02-10 23:19 ` [PATCH 1/3] iwlwifi: use pci registers defined in pci_regs.h Reinette Chatre
2009-02-10 23:19 ` [PATCH 2/3] iwlwifi: drop PCIe workaround applicable for development boards Reinette Chatre
2009-02-10 23:19 ` [PATCH 3/3] iwlwifi: fix FAT channel config for 5000 series Reinette Chatre
2009-02-11 16:16 ` [PATCH 0/3] iwlwifi driver updates 02/10/2009 reinette chatre
2009-02-11 16:25 ` John W. Linville [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=20090211162549.GA5082@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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).