public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] OMAP2+ PRCM: standardize PRCM macros
Date: Tue, 20 Apr 2010 16:29:20 -0700	[thread overview]
Message-ID: <87r5m9bt4f.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100420074204.3015.56304.stgit@localhost.localdomain> (Paul Walmsley's message of "Tue\, 20 Apr 2010 01\:45\:44 -0600")

Paul Walmsley <paul@pwsan.com> writes:

> This series standardizes the OMAP2+ PRCM register macro names to end
> in _SHIFT for bitshift counts and _MASK for bitmasks.  This is already the
> case for many of the macros, but others were unconverted; this series finally
> fixes those and their users in mainline.
>
> These patches will cause Kevin some merge pain, which is regrettable,
> but there seems to be no good time to do this sort of thing.

Merge pain accepted, this is a good cleanup.

That's the price I pay for having out of tree branches.

Kevin

      parent reply	other threads:[~2010-04-20 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20  7:45 [PATCH 0/4] OMAP2+ PRCM: standardize PRCM macros Paul Walmsley
2010-04-20  7:45 ` [PATCH 1/4] OMAP2 PRCM: convert OMAP2 PRCM macros to the _SHIFT/_MASK suffixes Paul Walmsley
2010-04-20  7:45 ` [PATCH 2/4] OMAP3 PRCM: convert OMAP3 " Paul Walmsley
2010-04-20  7:45 ` [PATCH 3/4] OMAP2+ PRCM: convert remaining " Paul Walmsley
2010-04-20  7:45 ` [PATCH 4/4] OMAP3: PM: PM_MPUGRPSEL writes should use GRPSEL macros, not EN macros Paul Walmsley
2010-04-20 23:29 ` Kevin Hilman [this message]

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=87r5m9bt4f.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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