From: Stephen Warren <swarren@wwwdotorg.org>
To: Venu Byravarasu <vbyravarasu@nvidia.com>
Cc: linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: tegra: fixing compilation error
Date: Thu, 13 Sep 2012 09:09:15 -0600 [thread overview]
Message-ID: <5051F71B.6030604@wwwdotorg.org> (raw)
In-Reply-To: <1347513385-14158-1-git-send-email-vbyravarasu@nvidia.com>
On 09/12/2012 11:16 PM, Venu Byravarasu wrote:
> As usb_phy.h got moved from mach to include/linux/usb
> and renamed as tegra_usb_phy.h, correcting it in the include
> path.
This should no longer be necessary assuming there's a new linux-next today.
(Note that I did point out this issue on our internal mailing list; are
you not subscribed to that?)
prev parent reply other threads:[~2012-09-13 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 5:16 [PATCH] arm: tegra: fixing compilation error Venu Byravarasu
2012-09-13 15:09 ` Stephen Warren [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=5051F71B.6030604@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=vbyravarasu@nvidia.com \
/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