From: Felix Fietkau <nbd@openwrt.org>
To: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
lrodriguez@atheros.com
Subject: Re: [PATCH v3 2/9] ath5k: Introduce ath5k_init_softc function as in ath9k
Date: Sat, 13 Nov 2010 02:50:34 +0100 [thread overview]
Message-ID: <4CDDEEEA.2030000@openwrt.org> (raw)
In-Reply-To: <1289577459-4276-3-git-send-email-Wojciech.Dubowik@neratec.com>
On 2010-11-12 4:57 PM, Wojciech Dubowik wrote:
> Split pci initialization into hardware specific
> functions and softc structure initialization.
> Make function naming similar to ones ath9k.
> Introduce ath_bus_opts in ath5k for later
> AHB bus integration.
>
> From: Felix Fietkau <nbd@openwrt.org>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
The 'From:' part only works if it's put in the first line of the message
body.
- Felix
parent reply other threads:[~2010-11-13 1:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1289577459-4276-3-git-send-email-Wojciech.Dubowik@neratec.com>]
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=4CDDEEEA.2030000@openwrt.org \
--to=nbd@openwrt.org \
--cc=Wojciech.Dubowik@neratec.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).