archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)"  <>
To: Linux kernel regressions list <>
Cc: "open list:HID CORE LAYER" <>,
	LKML <>
Subject: Re: [regression] Bug 217182 - Dell Latitude E7450 Trackpoint not working as expected
Date: Mon, 17 Apr 2023 13:46:27 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Link: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]

On 13.03.23 11:20, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
> I noticed a regression report in As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it by
> mail. Quoting from :

Tell regzbot about the fix for this:

#regzbot fix: 754ff5060daf5a1cf4474eff9b4edeb6c17ef7ab
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.

      parent reply	other threads:[~2023-04-17 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 10:20 [regression] Bug 217182 - Dell Latitude E7450 Trackpoint not working as expected Linux regression tracking (Thorsten Leemhuis)
2023-03-15  9:50 ` Thorsten Leemhuis
2023-03-19 16:51   ` Pali Rohár
2023-04-17 11:46 ` Linux regression tracking #update (Thorsten Leemhuis) [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).