All of lore.kernel.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download mbox.gz: |
* Re: Linux regressions report for mainline [2022-08-28]
  2022-08-28 19:08  7%   ` Thorsten Leemhuis
@ 2022-08-29  5:20  0%     ` Greg KH
  0 siblings, 0 replies; 2+ results
From: Greg KH @ 2022-08-29  5:20 UTC (permalink / raw)
  To: Thorsten Leemhuis; +Cc: Linus Torvalds, LKML, Linux regressions mailing list

On Sun, Aug 28, 2022 at 09:08:12PM +0200, Thorsten Leemhuis wrote:
> 
> 
> On 28.08.22 20:41, Linus Torvalds wrote:
> > On Sun, Aug 28, 2022 at 11:23 AM Regzbot (on behalf of Thorsten
> > Leemhuis) <regressions@leemhuis.info> wrote:
> >>
> >> Not sure, maybe it would have been good if the following fix would have
> >> found the way into rc3, as it seems more than just one or two people
> >> already stumbled over the regression fixed by it:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id a8e0f6b01b14b2e28ba144e112c883f03a3db2
> >> https://lore.kernel.org/all/?qœbffc7*
> > 
> > Neither of those links are valid for me.
> > 
> > "a8e0f6b01b14b2e28ba144e112c883f03a3db2" doesn't exist in linux-next.
> > never mind that that isn't valid link syntax anyway.
> > 
> > The lore.kernel.org link is also just random noise.
> > 
> > So I'm not actually sure what you are trying to say...
> 
> Sorry, you are right, I did something really stupid when preparing the
> mail (I manually modified one that was ready so send and already
> encoded...). Here are the links:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=13a8e0f6b01b14b2e28ba144e112c883f03a3db2
> https://lore.kernel.org/all/?q=9cbffc7*
> 
> But I just noticed that's not the only stupid thing I did, as the linked
> commit in next (13a8e0f6b01b) is part of a series:
> 
> https://lore.kernel.org/all/20220819221616.2107893-1-saravanak@google.com/
> 
> The series fixes the regression "Regression: PM: domains: Delete usage
> of driver_deferred_probe_check_state" that is in the list from regzbot:
> https://lore.kernel.org/all/DU0PR04MB941735271F45C716342D0410886B9@DU0PR04MB9417.eurprd04.prod.outlook.com/
> 
> But there are more reports, for example:
> https://lore.kernel.org/all/YvrkjH6%2FFpIzyAv+@euler/
> 
> Not sure if Greg didn't sent them to you because he think they need more
> time or because he's simply afk/busy and didn't manage to send pull
> requests.

I was busy, will get these out to Linus in the next few days.

thanks,

greg k-h

^ permalink raw reply	[relevance 0%]

* Re: Linux regressions report for mainline [2022-08-28]
  @ 2022-08-28 19:08  7%   ` Thorsten Leemhuis
  2022-08-29  5:20  0%     ` Greg KH
  0 siblings, 1 reply; 2+ results
From: Thorsten Leemhuis @ 2022-08-28 19:08 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: LKML, Linux regressions mailing list



On 28.08.22 20:41, Linus Torvalds wrote:
> On Sun, Aug 28, 2022 at 11:23 AM Regzbot (on behalf of Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>>
>> Not sure, maybe it would have been good if the following fix would have
>> found the way into rc3, as it seems more than just one or two people
>> already stumbled over the regression fixed by it:
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id a8e0f6b01b14b2e28ba144e112c883f03a3db2
>> https://lore.kernel.org/all/?qœbffc7*
> 
> Neither of those links are valid for me.
> 
> "a8e0f6b01b14b2e28ba144e112c883f03a3db2" doesn't exist in linux-next.
> never mind that that isn't valid link syntax anyway.
> 
> The lore.kernel.org link is also just random noise.
> 
> So I'm not actually sure what you are trying to say...

Sorry, you are right, I did something really stupid when preparing the
mail (I manually modified one that was ready so send and already
encoded...). Here are the links:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=13a8e0f6b01b14b2e28ba144e112c883f03a3db2
https://lore.kernel.org/all/?q=9cbffc7*

But I just noticed that's not the only stupid thing I did, as the linked
commit in next (13a8e0f6b01b) is part of a series:

https://lore.kernel.org/all/20220819221616.2107893-1-saravanak@google.com/

The series fixes the regression "Regression: PM: domains: Delete usage
of driver_deferred_probe_check_state" that is in the list from regzbot:
https://lore.kernel.org/all/DU0PR04MB941735271F45C716342D0410886B9@DU0PR04MB9417.eurprd04.prod.outlook.com/

But there are more reports, for example:
https://lore.kernel.org/all/YvrkjH6%2FFpIzyAv+@euler/

Not sure if Greg didn't sent them to you because he think they need more
time or because he's simply afk/busy and didn't manage to send pull
requests.

Guess waiting another week won't do too much harm.

Ciao, Thorsten

^ permalink raw reply	[relevance 7%]

Results 1-2 of 2 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2022-08-28 18:23     Linux regressions report for mainline [2022-08-28] Regzbot (on behalf of Thorsten Leemhuis)
2022-08-28 18:41     ` Linus Torvalds
2022-08-28 19:08  7%   ` Thorsten Leemhuis
2022-08-29  5:20  0%     ` Greg KH

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.