From: Christoph Hellwig <hch@lst.de>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Kalle Valo <kvalo@codeaurora.org>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: b43 / b43 legacy dma mask cleanups
Date: Tue, 25 Jun 2019 12:29:28 +0200 [thread overview]
Message-ID: <20190625102932.32257-1-hch@lst.de> (raw)
Hi all,
below are a few cleanups for the DMA mask handling. I came up with these
untested patches after looking through the code to debug the 32-bit pmac
30-bit dma issue involving b43legacy.
next reply other threads:[~2019-06-25 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:29 Christoph Hellwig [this message]
2019-06-25 10:29 ` [PATCH 1/4] b43legacy: remove b43legacy_dma_set_mask Christoph Hellwig
2019-06-25 21:45 ` Larry Finger
2019-06-27 11:38 ` Kalle Valo
2019-06-25 10:29 ` [PATCH 2/4] b43legacy: simplify engine type / DMA mask selection Christoph Hellwig
2019-06-25 10:29 ` [PATCH 3/4] b43: remove b43_dma_set_mask Christoph Hellwig
2019-06-25 10:29 ` [PATCH 4/4] b43: simplify engine type / DMA mask selection Christoph Hellwig
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=20190625102932.32257-1-hch@lst.de \
--to=hch@lst.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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).