From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH v3 14/17] media: i2c: imx290: Initialize runtime PM before subdev
Date: Tue, 28 Feb 2023 10:56:16 +0100 [thread overview]
Message-ID: <46d00d1a-9435-62d5-598d-49f0ea916f86@leemhuis.info> (raw)
In-Reply-To: <20230227175245.GA3728693@roeck-us.net>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 27.02.23 18:52, Guenter Roeck wrote:
> ---
> #regzbot ^introduced 02852c01f6540
>
[this mail is just fixing up an accidental use of "^"; this is kinda my
fault, the regzbot syntax is to confusing; I need to introduce something
like "regzbot forward" to make things more obvious, I just didn't get
around to it yet :-/ ]
#regzbot ^introduced 02852c01f6540
#regzbot title Build error in drivers/media/i2c/imx290.c if PM support
is disabled
#regzbot ignore-activity
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.
next prev parent reply other threads:[~2023-02-28 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230116144454.1012-1-laurent.pinchart@ideasonboard.com>
[not found] ` <20230116144454.1012-15-laurent.pinchart@ideasonboard.com>
2023-02-27 17:52 ` [PATCH v3 14/17] media: i2c: imx290: Initialize runtime PM before subdev Guenter Roeck
2023-02-28 9:56 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2023-03-20 10:50 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-02 14:21 ` Thorsten Leemhuis
2023-03-12 13:10 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-12 13:34 ` Laurent Pinchart
2023-03-12 13:59 ` Linux regression tracking (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=46d00d1a-9435-62d5-598d-49f0ea916f86@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 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).