From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/05] sh: pfc: Variable bitfield width and unlock reg patches
Date: Mon, 09 Jan 2012 00:34:13 +0000 [thread overview]
Message-ID: <20120109003413.GC25648@linux-sh.org> (raw)
On Wed, Dec 14, 2011 at 01:00:27AM +0900, Magnus Damm wrote:
> sh: pfc: Variable bitfield width and unlock reg patches
>
> [PATCH 01/05] sh: pfc: Add gpio_read_bit() for data register access
> [PATCH 02/05] sh: pfc: Convert index to field and value pair
> [PATCH 03/05] sh: pfc: Add config_reg_helper() function
> [PATCH 04/05] sh: pfc: Variable bitfield width config register support
> [PATCH 05/05] sh: pfc: Unlock register support
>
> Update the common PFC code to support r8a7779 by adding:
> - Variable bitfield width config register support (Patch 4)
> - Unlock register support (Patch 5)
>
> Patch 1-3 contain incremental changes needed for 4.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Depends on "[PATCH] sh: pfc: ioremap() support"
>
Applied to common/pfc, thanks.
next reply other threads:[~2012-01-09 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 0:34 Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-13 16:00 [PATCH 00/05] sh: pfc: Variable bitfield width and unlock reg patches Magnus Damm
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=20120109003413.GC25648@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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).