From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: "amba: Remove AMBA level regulator support" commit.
Date: Fri, 13 Apr 2012 09:37:01 +0100 [thread overview]
Message-ID: <20120413083700.GB3168@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120413012230.GA30438@windriver.com>
On Thu, Apr 12, 2012 at 09:22:31PM -0400, Paul Gortmaker wrote:
> is pointed at by git bisect for the u8500_defconfig build failure:
> If, like my earlier mail this week, this is something you've already
> fixed, then please provide me a link, and I'll gladly include that in
> the triage report, so you don't get needless extra mails about it.
Not me, but Linus W has a patch. No idea about a link off the top of my
head, google should turn something up I guess. It's exactly the same
sort of implicit header dependency issue that your cleanups keep
triggering.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120413/9f2a6a67/attachment.sig>
next prev parent reply other threads:[~2012-04-13 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 1:22 linux-next: "amba: Remove AMBA level regulator support" commit Paul Gortmaker
2012-04-13 2:01 ` Shawn Guo
2012-04-13 10:32 ` Russell King - ARM Linux
2012-04-13 10:44 ` Mark Brown
2012-04-13 10:49 ` Russell King - ARM Linux
2012-04-13 11:25 ` Mark Brown
2012-04-13 12:17 ` Fabio Estevam
2012-04-13 12:07 ` Mark Brown
2012-04-13 12:19 ` Russell King - ARM Linux
2012-04-13 14:04 ` Mark Brown
2012-04-13 12:30 ` Linus Walleij
2012-04-13 8:37 ` Mark Brown [this message]
2012-04-13 12:26 ` Linus Walleij
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=20120413083700.GB3168@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).