From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: sata_dwc_460ex build failures in -next
Date: Mon, 12 Jan 2015 13:07:05 +0000 [thread overview]
Message-ID: <20150112130705.GL4160@sirena.org.uk> (raw)
In-Reply-To: <1421067564.31903.3.camel@linux.intel.com>
On Mon, Jan 12, 2015 at 02:59:24PM +0200, Andy Shevchenko wrote:
> I just send a plug patch to disable compilation on ARMs.
Thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150112/12aead17/attachment.sig>
prev parent reply other threads:[~2015-01-12 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YAZyB-0007iE-CZ@debutante>
[not found] ` <20150112123655.GF4160@sirena.org.uk>
2015-01-12 12:50 ` sata_dwc_460ex build failures in -next Russell King - ARM Linux
2015-01-12 12:59 ` Andy Shevchenko
2015-01-12 13:07 ` 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=20150112130705.GL4160@sirena.org.uk \
--to=broonie@kernel.org \
--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