From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: Pending taprio fixes
Date: Thu, 17 Oct 2024 16:38:25 -0700 [thread overview]
Message-ID: <87a5f2cnbi.fsf@intel.com> (raw)
In-Reply-To: <20241017112546.208758-1-dmantipov@yandex.ru>
Hi,
Dmitry Antipov <dmantipov@yandex.ru> writes:
> Just one more friendly reminder.
>
Taking a look at:
https://patchwork.kernel.org/project/netdevbpf/list/?series=900198
A couple of process related things jump up:
1. The subject prefix was not set in the "cover letter", so perhaps
people/tools didn't see them as patches that should be considered,
also the lack of "net" in the subject prefix, made patchwork to guess
wrong, that this is targetting net-next;
2. You missed people from one of the patches CC list, running
get_maintainer.pl on the patches helps here;
3. You didn't add my "Acked-by" to this version;
Most probably, a mix of (1) and (2) was the reason that no one else
reacted to v5. I should have been more clear about those.
Cheers,
--
Vinicius
prev parent reply other threads:[~2024-10-17 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 11:25 Pending taprio fixes Dmitry Antipov
2024-10-17 11:25 ` [PATCH v6 1/2] net: sched: fix use-after-free in taprio_change() Dmitry Antipov
2024-10-17 11:25 ` [PATCH v6 2/2] net: sched: use RCU read-side critical section in taprio_dump() Dmitry Antipov
2024-10-17 23:38 ` Vinicius Costa Gomes [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=87a5f2cnbi.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=dmantipov@yandex.ru \
--cc=kuba@kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.