From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-mips@linux-mips.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
mpm@selenic.com, herbert@gondor.apana.org.au, wsa@the-dreams.de,
cernekee@gmail.com, Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH 0/4] hw_random: bcm63xx-rng: misc cleanups and reorg
Date: Mon, 16 Feb 2015 18:09:12 -0800 [thread overview]
Message-ID: <1424138956-11563-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi,
This patchset prepares the driver to be built on non-MIPS bcm63xx architectures
such as the ARM bcm63xx variants, thanks!
Although patch 3 touches a MIPS header file, there should be little to no
conflicts there if all patches went through the hw_random tree (is there one?)
Thanks!
Florian Fainelli (4):
hw_random: bcm63xx-rng: drop bcm_{readl,writel} macros
hw_random: bcm63xx-rng: move register definitions to driver
MIPS: BCM63xx: remove RSET_RNG register definitions
hw_random: bcm63xx-rng: use devm_* helpers
arch/mips/include/asm/mach-bcm63xx/bcm63xx_regs.h | 14 --------
drivers/char/hw_random/bcm63xx-rng.c | 43 +++++++++++------------
2 files changed, 21 insertions(+), 36 deletions(-)
--
2.1.0
next reply other threads:[~2015-02-17 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 2:09 Florian Fainelli [this message]
2015-02-17 2:09 ` [PATCH 1/4] hw_random: bcm63xx-rng: drop bcm_{readl,writel} macros Florian Fainelli
2015-02-17 2:09 ` [PATCH 2/4] hw_random: bcm63xx-rng: move register definitions to driver Florian Fainelli
2015-02-17 11:35 ` Sergei Shtylyov
2015-02-17 2:09 ` [PATCH 3/4] MIPS: BCM63xx: remove RSET_RNG register definitions Florian Fainelli
2015-02-17 2:09 ` [PATCH 4/4] hw_random: bcm63xx-rng: use devm_* helpers Florian Fainelli
2015-03-01 10:03 ` [PATCH 0/4] hw_random: bcm63xx-rng: misc cleanups and reorg Herbert Xu
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=1424138956-11563-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=cernekee@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mpm@selenic.com \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®