From: Mark Brown <broonie@kernel.org>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Applied "regmap: Use different lockdep class for each regmap init call" to the regmap tree
Date: Tue, 7 Jul 2015 20:08:56 +0100 [thread overview]
Message-ID: <20150707190856.GI11162@sirena.org.uk> (raw)
In-Reply-To: <E1ZCTO7-0005eh-7e@finisterre>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
On Tue, Jul 07, 2015 at 02:58:19PM +0100, Mark Brown wrote:
> The patch
>
> regmap: Use different lockdep class for each regmap init call
>
> has been applied to the regmap tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
...and reverted because it breaks the build.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-07 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 13:58 Applied "regmap: Use different lockdep class for each regmap init call" to the regmap tree Mark Brown
2015-07-07 19:08 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-16 12:13 Mark Brown
2015-07-16 12:18 ` Mark Brown
2015-08-07 14:00 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=20150707190856.GI11162@sirena.org.uk \
--to=broonie@kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-kernel@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