From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the regmap tree
Date: Wed, 27 Mar 2013 21:35:42 +1100 [thread overview]
Message-ID: <20130327213542.ebbac5f00544f89ae369e7cc@canb.auug.org.au> (raw)
In-Reply-To: <20130327102456.GR18316@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Wed, 27 Mar 2013 10:24:57 +0000 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> On Wed, Mar 27, 2013 at 03:47:37PM +1100, Stephen Rothwell wrote:
>
> > Introduced by commit 45c6a3e449ea ("regmap: cache: Provide a get address
> > of value operation").
>
> Don't know when you grabbed the tree but that's not what's there now.
Just before 10:30 am my time (UTC+1100) - so about 11 hours ago. I just
refetched and the regmap tree
(git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git#for-next)
is still the same as what I fetched this morning (top commit is
b32667515168 "Merge remote-tracking branch 'regmap/topic/range' into
regmap-next"). Probably just the mirroring delays.
Anyway, good to know it is fixed. Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-27 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 4:47 linux-next: build warnings after merge of the regmap tree Stephen Rothwell
2013-03-27 10:24 ` Mark Brown
2013-03-27 10:35 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-17 4:39 Stephen Rothwell
2015-07-17 9:44 ` Nariman Poushin
2015-07-17 10:34 ` Mark Brown
2015-07-17 15:29 ` Nariman Poushin
2015-07-17 16:45 ` Charles Keepax
2011-08-09 3:21 Stephen Rothwell
2011-08-09 15:01 ` Mark Brown
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=20130327213542.ebbac5f00544f89ae369e7cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).