From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 10/10] phy: tegra: Changes for v5.7-rc1
Date: Thu, 19 Mar 2020 15:41:35 +0100 [thread overview]
Message-ID: <20200319144135.GA3266151@ulmo> (raw)
In-Reply-To: <20200316134850.GB3825456@ulmo>
[-- Attachment #1.1: Type: text/plain, Size: 1350 bytes --]
On Mon, Mar 16, 2020 at 02:48:50PM +0100, Thierry Reding wrote:
> On Fri, Mar 13, 2020 at 05:58:48PM +0100, Thierry Reding wrote:
> > Hi ARM SoC maintainers,
> >
> > The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
> >
> > Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.7-phy
> >
> > for you to fetch changes up to 04c929223d1db6ad4ba8e4c23122e1052f670c2e:
> >
> > phy: tegra: xusb: Don't warn on probe defer (2020-03-13 09:17:50 +0100)
> >
> > This is a dependency for the USB changes that are also part of this
> > series of pull requests, so it was deemed easier to take this all
> > through the ARM SoC tree. The patches have all been acked by Kishon.
>
> Please don't merge this just yet. Stephen reported today that this was
> breaking the build in linux-next because of a conflict with the USB
> tree. I'll rebase this on top of Greg's usb-next branch and resend the
> pull request.
>
> Sorry for the inconvenience.
I've pushed an updated version of this as tegra-for-5.7-phy-v2. However,
it's also included as a dependency in a USB branch for which I've sent a
PR to Greg, so I don't think you'll need to merge this after all.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-19 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 16:58 [GIT PULL 01/10] dt-bindings: Changes for v5.7-rc1 Thierry Reding
2020-03-13 16:58 ` [GIT PULL 02/10] firmware: tegra: " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 03/10] soc/tegra: " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 04/10] memory: tegra: " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 05/10] ARM: tegra: Core changes " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 06/10] ARM: tegra: Device tree " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 07/10] ARM: tegra: Default configuration " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 08/10] arm64: tegra: Device tree " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 09/10] cpuidle: tegra: Changes " Thierry Reding
2020-03-13 16:58 ` [GIT PULL 10/10] phy: " Thierry Reding
2020-03-16 13:48 ` Thierry Reding
2020-03-19 14:41 ` Thierry Reding [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=20200319144135.GA3266151@ulmo \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).