From: Marek Vasut <marek.vasut@mailbox.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Mathias Nyman <mathias.nyman@intel.com>,
Vinod Koul <vkoul@kernel.org>,
stable@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] usb: renesas-xhci: Fix External ROM access timeouts
Date: Tue, 29 Jul 2025 05:09:55 +0200 [thread overview]
Message-ID: <b9c9ba83-6da2-4295-b058-a0520c9df806@mailbox.org> (raw)
In-Reply-To: <2025072828-suspect-work-12ca@gregkh>
On 7/28/25 6:18 AM, Greg Kroah-Hartman wrote:
[...]
>> Fixes: 2478be82de44 ("usb: renesas-xhci: Add ROM loader for uPD720201")
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
>> ---
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: Mathias Nyman <mathias.nyman@intel.com>
>> Cc: Vinod Koul <vkoul@kernel.org>
>> Cc: <stable@vger.kernel.org>
[...]
> - You have marked a patch with a "Fixes:" tag for a commit that is in an
> older released kernel, yet you do not have a cc: stable line in the
> signed-off-by area at all, which means that the patch will not be
> applied to any older kernel releases. To properly fix this, please
> follow the documented rules in the
> Documentation/process/stable-kernel-rules.rst file for how to resolve
> this.
Maybe the bot should take into consideration Cc: stable below the ---
too ? Or is that considered invalid ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2025-07-29 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 15:44 [PATCH] usb: renesas-xhci: Fix External ROM access timeouts Marek Vasut
2025-07-28 4:18 ` Greg Kroah-Hartman
2025-07-29 3:09 ` Marek Vasut [this message]
2025-07-29 5:03 ` Greg Kroah-Hartman
2025-07-29 7:11 ` Geert Uytterhoeven
2025-07-29 7:55 ` Greg Kroah-Hartman
2025-07-29 10:17 ` Michał Pecio
2025-08-02 22:30 ` Marek Vasut
2025-07-29 15:20 ` Mathias Nyman
2025-08-02 22:54 ` Marek Vasut
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=b9c9ba83-6da2-4295-b058-a0520c9df806@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stable@vger.kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).