From: Jakub Kicinski <kuba@kernel•org>
To: "Nelson, Shannon" <shannon.nelson@amd•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, edumazet@google•com,
pabeni@redhat•com, brett.creeley@amd•com, drivers@pensando•io
Subject: Re: [PATCH net 0/7] ionic: small driver fixes
Date: Mon, 4 Dec 2023 10:35:03 -0800 [thread overview]
Message-ID: <20231204103503.757bafb7@kernel.org> (raw)
In-Reply-To: <6c5069f1-d689-438b-9c1c-ba3dd62fdb4d@amd.com>
On Mon, 4 Dec 2023 10:23:40 -0800 Nelson, Shannon wrote:
> Okay, you would prefer most of these as net-next, and you like the Fixes
> tags, but normally if there are Fixes tags they should be in net. So,
> do you want the Fixes tags removed when these patches are sent to net-next?
Yes, that's right. What goes to net-next should have Fixes tag stripped.
If you want to preserve the reference for your own needs, you can say
something like:
This code was introduced in commit ...
Just not a bona fide Fixes tag, please.
prev parent reply other threads:[~2023-12-04 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 0:05 [PATCH net 0/7] ionic: small driver fixes Shannon Nelson
2023-12-01 0:05 ` [PATCH net 1/7] ionic: fix snprintf format length warning Shannon Nelson
2023-12-01 0:05 ` [PATCH net 2/7] ionic: Use cached VF attributes Shannon Nelson
2023-12-01 0:05 ` [PATCH net 3/7] ionic: set ionic ptr before setting up ethtool ops Shannon Nelson
2023-12-01 0:05 ` [PATCH net 4/7] ionic: Don't check null when calling vfree() Shannon Nelson
2023-12-01 0:05 ` [PATCH net 5/7] ionic: Make the check for Tx HW timestamping more obvious Shannon Nelson
2023-12-01 0:05 ` [PATCH net 6/7] ionic: Fix dim work handling in split interrupt mode Shannon Nelson
2023-12-01 0:05 ` [PATCH net 7/7] ionic: Re-arrange ionic_intr_info struct for cache perf Shannon Nelson
2023-12-01 4:19 ` [PATCH net 0/7] ionic: small driver fixes Florian Fainelli
2023-12-01 17:20 ` Nelson, Shannon
2023-12-02 1:42 ` Jakub Kicinski
2023-12-04 18:23 ` Nelson, Shannon
2023-12-04 18:35 ` Jakub Kicinski [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=20231204103503.757bafb7@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=brett.creeley@amd$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=drivers@pensando$(echo .)io \
--cc=edumazet@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=shannon.nelson@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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