From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org,
linux-tegra <linux-tegra@vger.kernel.org>,
j-keerthy@ti.com
Subject: Re: [PATCH 5.1 000/138] 5.1.18-stable review
Date: Sat, 13 Jul 2019 16:31:54 +0200 [thread overview]
Message-ID: <20190713143154.GB7695@kroah.com> (raw)
In-Reply-To: <5f897de4-b423-c8a2-6823-d0227eb7bd38@nvidia.com>
On Sat, Jul 13, 2019 at 10:16:58AM +0100, Jon Hunter wrote:
>
> On 12/07/2019 16:30, Greg Kroah-Hartman wrote:
> > On Fri, Jul 12, 2019 at 02:26:57PM +0100, Jon Hunter wrote:
> >> Hi Greg,
> >>
> >> On 12/07/2019 13:17, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 5.1.18 release.
> >>> There are 138 patches in this series, all will be posted as a response
> >>> to this one. If anyone has any issues with these being applied, please
> >>> let me know.
> >>>
> >>> Responses should be made by Sun 14 Jul 2019 12:14:36 PM UTC.
> >>> Anything received after that time might be too late.
> >>>
> >>> The whole patch series can be found in one patch at:
> >>> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.18-rc1.gz
> >>> or in the git tree and branch at:
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.1.y
> >>> and the diffstat can be found below.
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>>
> >>> -------------
> >>> Pseudo-Shortlog of commits:
> >>
> >> ...
> >>
> >>> Keerthy <j-keerthy@ti.com>
> >>> ARM: dts: dra71x: Disable usb4_tm target module
> >>
> >> ...
> >>
> >>> Keerthy <j-keerthy@ti.com>
> >>> ARM: dts: dra76x: Disable usb4_tm target module
> >>
> >> The above commits are generating the following compilation errors for
> >> ARM ...
> >>
> >> Error:
> >> /dvs/git/dirty/git-master_l4t-upstream/kernel/arch/arm/boot/dts/dra71x.dtsi:15.1-9
> >> Label or path usb4_tm not found
> >>
> >> Error:
> >> /dvs/git/dirty/git-master_l4t-upstream/kernel/arch/arm/boot/dts/dra76x.dtsi:89.1-9
> >> Label or path usb4_tm not found
> >>
> >> After reverting these two, I no longer see these errors.
> >
> > Both are now dropped, thanks. I'll push out a -rc2 with that changed.
>
> Hmmm ... -rc2 still not building ...
>
> Error:
> /dvs/git/dirty/git-master_l4t-upstream/kernel/arch/arm/boot/dts/dra71x.dtsi:11.1-11
> Label or path rtctarget not found
> Error:
> /dvs/git/dirty/git-master_l4t-upstream/kernel/arch/arm/boot/dts/dra71x.dtsi:15.1-9
> Label or path usb4_tm not found
>
> I still see the following commit in -rc2 ...
>
> commit 0caa574b3244cd863dd74bde680a6309cb8803ad
> Author: Keerthy <j-keerthy@ti.com>
> Date: Fri May 17 06:44:09 2019 +0530
>
> ARM: dts: dra71x: Disable usb4_tm target module
>
> In -rc1 I see there were 4 changes from Keerthy, any chance you reverted
> one of the rtc patches and not the above? Looks like the following is
> missing from -rc2 ...
>
> Keerthy <j-keerthy@ti.com>
> ARM: dts: dra76x: Disable rtc target module
Sorry, I dropped one, but not the other. Both now gone.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-13 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190712121628.731888964@linuxfoundation.org>
2019-07-12 13:26 ` [PATCH 5.1 000/138] 5.1.18-stable review Jon Hunter
2019-07-12 15:30 ` Greg Kroah-Hartman
2019-07-12 20:21 ` Guenter Roeck
2019-07-13 8:22 ` Greg Kroah-Hartman
2019-07-13 13:16 ` Guenter Roeck
2019-07-13 14:25 ` Greg Kroah-Hartman
2019-07-13 9:16 ` Jon Hunter
2019-07-13 14:31 ` Greg Kroah-Hartman [this message]
2019-07-13 18:56 ` Jon Hunter
2019-07-14 6:01 ` Greg Kroah-Hartman
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=20190713143154.GB7695@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=j-keerthy@ti.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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