All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-arm-kernel@lists.infradead.org,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: devicetree@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Boot failure regression on 6.0.10 stable kernel on iMX7 #forregzbot
Date: Thu, 1 Dec 2022 13:06:22 +0100	[thread overview]
Message-ID: <877f72a1-289d-1c39-e413-7332baa35dd1@leemhuis.info> (raw)
In-Reply-To: <Y4dgBTGNWpM6SQXI@francesco-nb.int.toradex.com>

[Note: this mail contains only information relevant for regzbot, the
Linux kernel regression tracking bot. That's why I removed most
recipients of the quoted mail and only left what looked like a mailing
lists. These mails contain '#forregzbot' in the subject, to make them
easy to spot and filter out.]

On 30.11.22 14:52, Francesco Dolcini wrote:
> it looks like commit 753395ea1e45 ("ARM: dts: imx7: Fix NAND controller
> size-cells"), that was backported to stable 6.0.10, introduce a boot
> regression on colibri-imx7, at least.
> [...]

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced 753395ea1e45
#regzbot title ARM: dts: imx7: Boot failure on iMX7
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

WARNING: multiple messages have this Message-ID (diff)
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-arm-kernel@lists.infradead.org,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: devicetree@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Boot failure regression on 6.0.10 stable kernel on iMX7 #forregzbot
Date: Thu, 1 Dec 2022 13:06:22 +0100	[thread overview]
Message-ID: <877f72a1-289d-1c39-e413-7332baa35dd1@leemhuis.info> (raw)
In-Reply-To: <Y4dgBTGNWpM6SQXI@francesco-nb.int.toradex.com>

[Note: this mail contains only information relevant for regzbot, the
Linux kernel regression tracking bot. That's why I removed most
recipients of the quoted mail and only left what looked like a mailing
lists. These mails contain '#forregzbot' in the subject, to make them
easy to spot and filter out.]

On 30.11.22 14:52, Francesco Dolcini wrote:
> it looks like commit 753395ea1e45 ("ARM: dts: imx7: Fix NAND controller
> size-cells"), that was backported to stable 6.0.10, introduce a boot
> regression on colibri-imx7, at least.
> [...]

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced 753395ea1e45
#regzbot title ARM: dts: imx7: Boot failure on iMX7
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-12-01 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 13:52 Boot failure regression on 6.0.10 stable kernel on iMX7 Francesco Dolcini
2022-11-30 13:52 ` Francesco Dolcini
2022-11-30 14:41 ` Marek Vasut
2022-11-30 14:41   ` Marek Vasut
2022-11-30 20:51   ` Francesco Dolcini
2022-11-30 20:51     ` Francesco Dolcini
2022-11-30 22:59     ` Marek Vasut
2022-11-30 22:59       ` Marek Vasut
2022-12-01 11:03       ` Francesco Dolcini
2022-12-01 11:03         ` Francesco Dolcini
2022-12-01 11:03         ` Francesco Dolcini
2022-12-01 11:25         ` Marek Vasut
2022-12-01 11:25           ` Marek Vasut
2022-12-01 11:25           ` Marek Vasut
2022-12-01 15:45           ` Francesco Dolcini
2022-12-01 15:45             ` Francesco Dolcini
2022-12-01 15:45             ` Francesco Dolcini
2022-12-01 22:00             ` Marek Vasut
2022-12-01 22:00               ` Marek Vasut
2022-12-01 22:00               ` Marek Vasut
2022-12-01 12:06 ` Thorsten Leemhuis [this message]
2022-12-01 12:06   ` Boot failure regression on 6.0.10 stable kernel on iMX7 #forregzbot Thorsten Leemhuis

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=877f72a1-289d-1c39-e413-7332baa35dd1@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.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 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.