From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
Mikko Perttunen
<mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ahci_tegra build failure in Linus' tree
Date: Thu, 21 Aug 2014 14:32:37 -0500 [thread overview]
Message-ID: <20140821193237.GB6168@mtj.dyndns.org> (raw)
In-Reply-To: <20140821185352.GP24407-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Hello,
On Thu, Aug 21, 2014 at 01:53:52PM -0500, Mark Brown wrote:
> On Thu, Aug 21, 2014 at 01:32:29PM +0100, Build bot for Mark Brown wrote:
>
> > ../drivers/ata/ahci_tegra.c:27:35: fatal error: linux/tegra-powergate.h: No such file or directory
>
> ARM allmodconfig currently fails to build in mainline due to the above
> error. It has been fixed in -next by Mikko Perttunen in commit
> 0e5740770f34381b (ata: ahci_tegra: Change include to fix compilation)
> but it's not clear to me if that's on it's way to Linus - it'd be great
> if it could be.
Will push it out right away.
Thanks.
--
tejun
prev parent reply other threads:[~2014-08-21 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XKRXZ-0000vL-4b@cassiel.sirena.org.uk>
[not found] ` <E1XKRXZ-0000vL-4b-AwNWNkNSnF8YV1p1LO3TTN73F7V6hmMc@public.gmane.org>
2014-08-21 18:53 ` ahci_tegra build failure in Linus' tree Mark Brown
[not found] ` <20140821185352.GP24407-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-08-21 19:32 ` Tejun Heo [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=20140821193237.GB6168@mtj.dyndns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).