public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.1 00/25] 6.1.1-rc1 review
Date: Wed, 21 Dec 2022 17:12:03 +0100	[thread overview]
Message-ID: <Y6MwU0kvczAkzT6C@kroah.com> (raw)
In-Reply-To: <20221220161135.GA1983195@roeck-us.net>

On Tue, Dec 20, 2022 at 08:11:35AM -0800, Guenter Roeck wrote:
> On Tue, Dec 20, 2022 at 04:10:55PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Dec 20, 2022 at 07:00:49AM -0800, Guenter Roeck wrote:
> > > On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.1 release.
> > > > There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000.
> > > > Anything received after that time might be too late.
> > > > 
> > > 
> > > Build results:
> > > 	total: 155 pass: 155 fail: 0
> > > Qemu test results:
> > > 	total: 500 pass: 498 fail: 2
> > > Failed tests:
> > > 	arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs
> > > 	arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
> > > 
> > > The failure bisects to commit e013ba1e4e12 ("usb: ulpi: defer ulpi_register on
> > > ulpi_read_id timeout") and is inherited from mainline. Reverting the offending
> > > patch fixes the problem.
> > 
> > Odd, yet that same commit works just fine on 6.0 and 5.15 and 5.10?  I
> > hadn't had any reports of this being an issue on Linus's tree either,
> > did I miss those?
> > 
> 
> I testbed has a bad hair day. The reports for the other branches are wrong.
> I restarted the tests and expect them to fail there as well. Sorry for that.

No worries, I've deleted this patch from all branches now, thanks.

greg k-h

  parent reply	other threads:[~2022-12-21 16:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 19:22 [PATCH 6.1 00/25] 6.1.1-rc1 review Greg Kroah-Hartman
2022-12-20  0:15 ` Shuah Khan
2022-12-20  0:21 ` Florian Fainelli
2022-12-20  4:45 ` Bagas Sanjaya
2022-12-20  7:41 ` Ron Economos
2022-12-20  9:20 ` Rudi Heitbaum
2022-12-20 10:51 ` Naresh Kamboju
2022-12-20 12:26 ` Sudip Mukherjee (Codethink)
2022-12-20 14:31   ` Sudip Mukherjee
2022-12-21 18:19     ` Greg Kroah-Hartman
2022-12-20 15:00 ` Guenter Roeck
2022-12-20 15:10   ` Greg Kroah-Hartman
2022-12-20 16:11     ` Guenter Roeck
2022-12-21  6:34       ` Jiri Slaby
2022-12-21 18:20         ` Greg Kroah-Hartman
2022-12-22  8:07         ` Thorsten Leemhuis
2022-12-21 16:12       ` Greg Kroah-Hartman [this message]
2022-12-20 18:09 ` Jon Hunter
2022-12-20 18:57 ` Allen Pais
2022-12-21  1:13 ` Slade Watkins
2022-12-21 16:18 ` Justin Forbes
2022-12-29  7:36 ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2022-12-19 19:58 Ronald Warsow

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=Y6MwU0kvczAkzT6C@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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