mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Cc: H Hartley Sweeten <hsweeten@visionengravers.com>,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	Arnd Bergmann <arnd@kernel.org>,
	stable@vger.kernel.org, Ian Abbott <abbotti@mev.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "comedi: add HAS_IOPORT dependencies"
Date: Tue, 12 Sep 2023 12:39:28 +0200	[thread overview]
Message-ID: <516005ff-636e-4aa9-9bcb-76902c09f855@leemhuis.info> (raw)
In-Reply-To: <2023091226-foe-reanalyze-b859@gregkh>

On 12.09.23 12:13, Greg Kroah-Hartman wrote:
> On Tue, Sep 12, 2023 at 11:44:39AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 05.09.23 11:09, Ian Abbott wrote:
>>> This reverts commit b5c75b68b7ded84d4c82118974ce3975a4dcaa74.
>>>
>>> The commit makes it impossible to select configuration options that
>>> depend on COMEDI_8254, COMEDI_DAS08, COMEDI_NI_LABPC, or
>>> COMEDI_AMPLC_DIO200 options due to changing 'select' directives to
>>> 'depends on' directives and there being no other way to select those
>>> codependent configuration options.
>>>
>>> Fixes: b5c75b68b7de ("comedi: add HAS_IOPORT dependencies")
>>> Cc: Niklas Schnelle <schnelle@linux.ibm.com>
>>> Cc: Arnd Bergmann <arnd@kernel.org>
>>> Cc: <stable@vger.kernel.org> # v6.5+
>>> Acked-by: Arnd Bergmann <arnd@kernel.org>
>>> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
>>
>> Hmmm, that fix for a regression from the 6.5 cycle was posted a week ago
>> but didn't get a single reply afaics and hasn't hit next.
>>
>> Greg, is this still in your to-review queue and just delayed due to the
>> merge window? Or are you waiting for something? A ACK fromn Niklas
>> maybe? Or a newer patch to address the kernel test robot report in case
>> its relevant?
> 
> The merge window "freeze" ended on Monday, give me a chance to catch up
> with patches please, this is part of my very large todo mbox:
> 
> 	$ mdfrm -c ~/mail/todo/
> 	1637 messages in /home/gregkh/mail/todo/

Well, I know that you deal with a lot of patches and often wonder how
you manage to do all that great work, but nevertheless please allow me
to ask:

I assume that that not all of those 1600+ patches are fixes for
regressions, so should a revert for a very recent regression be in a
different mbox with a slightly higher priority[1] to get handled before
the others?

Ciao, Thorsten

[1] for most other developers I would have said "highest priory", but I
assume in your case there are still more important things

  reply	other threads:[~2023-09-12 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  9:09 Ian Abbott
2023-09-12  9:44 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-12 10:13   ` Greg Kroah-Hartman
2023-09-12 10:39     ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-09-12 10:48       ` Greg Kroah-Hartman
2023-09-12 10:55         ` 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=516005ff-636e-4aa9-9bcb-76902c09f855@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=abbotti@mev.co.uk \
    --cc=arnd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=schnelle@linux.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®