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,
Stephen Warren <swarren@nvidia.com>
Subject: Re: linux-next: build failure after merge of the regmap tree
Date: Wed, 11 Apr 2012 09:17:11 +0100 [thread overview]
Message-ID: <20120411081711.GB3163@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120411141346.3c4dd8e481d052b583ac95b6@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Wed, Apr 11, 2012 at 02:13:46PM +1000, Stephen Rothwell wrote:
> Caused by commit f01ee60fffa4 ("regmap: implement register striding").
> Please build test ...
Mainline *still* doesn't build with the .configs I routinely use.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-11 8:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 4:13 linux-next: build failure after merge of the regmap tree Stephen Rothwell
2012-04-11 8:17 ` Mark Brown [this message]
2012-04-11 22:07 ` mainline build failure (Was: Re: linux-next: build failure after merge of the regmap tree) Stephen Rothwell
2012-04-12 15:46 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 7:24 linux-next: build failure after merge of the regmap tree Stephen Rothwell
2020-11-30 17:59 ` Mark Brown
2020-11-30 18:07 ` Pierre-Louis Bossart
2020-11-30 18:11 ` Mark Brown
2020-11-30 18:21 ` Pierre-Louis Bossart
2017-11-02 0:57 Stephen Rothwell
2012-02-27 4:05 Stephen Rothwell
[not found] <C3AE124F08223B42BC95AEB82F0F6CED1F9D0895@KCHJEXMB01.kpit.com>
2011-12-15 9:25 ` Ashish Jangam
2011-12-15 9:25 ` Ashish Jangam
2011-12-15 18:25 ` Grant Likely
2011-12-16 7:19 ` Ashish Jangam
2011-12-16 8:11 ` Grant Likely
2011-12-16 8:15 ` Ashish Jangam
2011-12-16 8:25 ` Grant Likely
2011-12-15 6:17 Stephen Rothwell
2011-12-15 6:05 Stephen Rothwell
2011-12-15 6:17 ` Mark Brown
2011-12-15 6:24 ` Ashish Jangam
2011-12-15 6:24 ` Ashish Jangam
2011-09-29 5:18 Stephen Rothwell
2011-09-29 9:43 ` 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=20120411081711.GB3163@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 \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.