linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Wojciech Dubowik <dubowoj@neratec.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/9] ath5k: AHB port. Use generic DMA instead of PCI API.
Date: Thu, 11 Nov 2010 10:18:47 -0800	[thread overview]
Message-ID: <AANLkTinpan-k4J2Z-gB3vcRMHKpwtg0-Ra42S9WuS9Rr@mail.gmail.com> (raw)
In-Reply-To: <23232015.1011289487455461.JavaMail.wlan@CHBU500181>

On Thu, Nov 11, 2010 at 6:57 AM, Wojciech Dubowik <dubowoj@neratec.com> wrote:
> General comments for AHB bus support in ath5k:
>  - most of the original patches came from Felix Fetikau. I have used them as a reference and ported to current git tree
>  - tried with access point functionality with WPA2 and without encryption
>  - tested on AR5312 for AHB and AR5414 and AR5212 for PCI
>  - compat wireless from openwrt was used for testing these patches
>  - last two patches have to be applied together because otherwise hardware will crash on reset if
>  only number 9 is committed. I have kept them separated for better visibility
>
>
>
> Generic DMA is needed for AHB support.
>
> Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>

Nice! You want to send these patches in a series as you have but use a
cover letter to introduce and explain the series. This patch's commit
log should only note that this uses the Generic DMA APIs in order to
later support AHB. You can get yourself a cover letter using git
format-patch --cover-letter. For more elaborate examples check out:

http://wireless.kernel.org/en/developers/Documentation/git-guide

  Luis

  reply	other threads:[~2010-11-11 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17888045.991289487433290.JavaMail.wlan@CHBU500181>
2010-11-11 14:57 ` [PATCH 1/9] ath5k: AHB port. Use generic DMA instead of PCI API Wojciech Dubowik
2010-11-11 18:18   ` Luis R. Rodriguez [this message]
2010-11-12 18:56     ` Bob Copeland
2010-11-24 16:46   ` John W. Linville

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=AANLkTinpan-k4J2Z-gB3vcRMHKpwtg0-Ra42S9WuS9Rr@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=dubowoj@neratec.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).