From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: bad commit in the regmap tree
Date: Thu, 1 Mar 2012 16:17:52 +0000 [thread overview]
Message-ID: <20120301161752.GB10915@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120301105425.ef188f8724204c55ec805929@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On Thu, Mar 01, 2012 at 10:54:25AM +1100, Stephen Rothwell wrote:
> I noticed that commit 0308333a9987 ("regmap: Add stub for
> regcache_sync_region()") is the same as its parent commit 868d3fdeaae9
> ("regmap: Add stub for regcache_sync_region()"). So the function
> regcache_sync_region() has been added to include/linux/regmap.h twice
> (the context is not sufficient to stop the patch applying twice).
Oh, I had thought I'd pushed it out already but was just trusting rebase
that I hadn't. Fixed now.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-01 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 23:54 linux-next: bad commit in the regmap tree Stephen Rothwell
2012-03-01 16:17 ` Mark Brown [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=20120301161752.GB10915@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).