From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Subject: Re: matroxfb: cannot determine memory size
Date: Thu, 16 Feb 2023 13:50:07 +0100 [thread overview]
Message-ID: <9ec958e1-ae6e-d50a-2f15-008267c0a578@leemhuis.info> (raw)
In-Reply-To: <dc0b1487-04f9-5a2f-e0f8-d157a74b6bcb@molgen.mpg.de>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 16.12.22 12:58, Paul Menzel wrote:
> [Cc: +regressions@, +stable@]
>
> #regzbot ^introduced: 62d89a7d49afe46e6b9bbe9e23b004ad848dbde4
#regzbot fix: f685dd7a8025f
(/me missed that in during the festive season and didn't notice until now)
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
#regzbot ignore-activity
next prev parent reply other threads:[~2023-02-16 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:39 matroxfb: cannot determine memory size Paul Menzel
2022-12-15 23:02 ` Helge Deller
2022-12-16 11:58 ` Paul Menzel
2022-12-16 21:21 ` Helge Deller
2022-12-19 11:58 ` Paul Menzel
2022-12-19 12:19 ` Helge Deller
2023-02-16 12:50 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2022-12-16 12:27 ` Thomas Zimmermann
2022-12-16 13:16 ` Why is mgag200 not used over matroxfb? (was: matroxfb: cannot determine memory size) Paul Menzel
2023-01-03 16:20 ` Why is mgag200 not used over matroxfb? Paul Menzel
2023-01-04 8:19 ` Thomas Zimmermann
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=9ec958e1-ae6e-d50a-2f15-008267c0a578@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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.