From: Felipe Balbi <balbi@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: <balbi@ti.com>, <tj@kernel.org>, <thierry.reding@gmail.com>,
<linux-ide@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ata: ahci: tegra: fix build error
Date: Thu, 21 Aug 2014 14:21:34 -0500 [thread overview]
Message-ID: <20140821192134.GO11146@saruman.home> (raw)
In-Reply-To: <53F645BA.4000402@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Thu, Aug 21, 2014 at 01:17:14PM -0600, Stephen Warren wrote:
> On 08/21/2014 01:08 PM, Felipe Balbi wrote:
> >Currently, ahci_tegra doesn't build because it includes a file that
> >doesn't exist.
> >
> >The problem is that first commit 306a7f9 (ARM: tegra: Move includes to
> >include/soc/tegra) renamed include/linux/tegra-powergate.h to
> >include/soc/tegra/powergate.h.
> >
> >Later commit 7232398 (ARM: tegra: Convert PMC to a driver) renamed
> >include/soc/tegra/powergate.h to include/soc/tegra/pmc.h and neither
> >commits fixed drivers/ata/ahci_tegra.c.
> >
> >Fix that so the driver has a chance of building. With current kernels.
> >
> >Cc: <stable@vger.kernel.org> # v3.16
>
> This driver first appeared in v3.17-rc1.
hmm... weird, git describe told v3.16-rc1 :-s
> This patch has already been sent, and apparently applied:
>
> https://lkml.org/lkml/2014/8/16/36
aha, thanks.
> I wonder if libata/for-3.17-fixes isn't in linux-next?
it is, it's just that I was build testing my branch which is based off
of v3.17-rc1 as of now.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-21 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 19:08 Felipe Balbi
2014-08-21 19:17 ` Stephen Warren
2014-08-21 19:21 ` Felipe Balbi [this message]
2014-08-21 19:31 ` Tejun Heo
2014-08-21 19:18 ` Felipe Balbi
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=20140821192134.GO11146@saruman.home \
--to=balbi@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=tj@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
all inboxes | Powered by JetHome®