From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Phil Sutter" <phil@nwl.cc>, "René Rebe" <rene@exactco.de>,
netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: [PATCH V2] r8169: fix RTL8117 Wake-on-Lan in DASH mode
Date: Thu, 4 Dec 2025 21:18:59 +0100 [thread overview]
Message-ID: <b9e48b10-6654-4239-a170-8cd7bf77fe0b@gmail.com> (raw)
In-Reply-To: <aTGpceAK0CRgKDPG@orbyte.nwl.cc>
On 12/4/2025 4:32 PM, Phil Sutter wrote:
> On Tue, Dec 02, 2025 at 07:06:02PM +0100, Heiner Kallweit wrote:
>> On 12/2/2025 6:45 PM, René Rebe wrote:
>>> On Tue, 2 Dec 2025 18:19:02 +0100, Heiner Kallweit <hkallweit1@gmail.com> wrote:
> [...]
>>>> - cc stable
>>>
>>> I was under the impression this is automatic when patches are merged
>>> with Fixes:, no? Do I need to manually cc stable? Nobody ever asked me
>>> for that before.
>>>
>> https://docs.kernel.org/process/maintainer-netdev.html
>> See 1.5.7
>
> Which points to
> https://docs.kernel.org/process/stable-kernel-rules.html#stable-kernel-rules
> and the Option 1 instructions read: "Note, such tagging is unnecessary
> if the stable team can derive the appropriate versions from Fixes:
> tags."
>
This is about something different. "such tagging" refers to providing
applicable kernel versions like in the example:
Cc: <stable@vger.kernel.org> # 3.3.x
> Cheers, Phil
prev parent reply other threads:[~2025-12-04 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 15:16 [PATCH V2] r8169: fix RTL8117 Wake-on-Lan in DASH mode René Rebe
2025-12-02 17:19 ` Heiner Kallweit
2025-12-02 17:45 ` René Rebe
2025-12-02 18:06 ` Heiner Kallweit
2025-12-04 15:32 ` Phil Sutter
2025-12-04 20:18 ` Heiner Kallweit [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:
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=b9e48b10-6654-4239-a170-8cd7bf77fe0b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=phil@nwl.cc \
--cc=rene@exactco.de \
/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).