From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, arkadiusz.kubalewski@intel.com,
vadim.fedorenko@linux.dev
Subject: Re: [patch net-next] dpll: spec: use proper enum for pin capabilities attribute
Date: Wed, 13 Mar 2024 08:31:11 -0700 [thread overview]
Message-ID: <20240313083111.4591590d@kernel.org> (raw)
In-Reply-To: <ZfG_C6wi4EeBj9l3@nanopsycho>
On Wed, 13 Mar 2024 15:58:19 +0100 Jiri Pirko wrote:
> >> I think I have his private email, let me follow up off list and either
> >> put his @intel.com address in the mailmap or the ignore list.
> >
> >Hi Jiri! Do you still want to add him to the ignore list?
>
> If we are going to start to use .get_maintainer.ignore for this purpose,
> yes please. Should I send the patch? net-next is closed anyway...
With the current tooling I think it's the best we can do.
If someone disagrees let them shout at us.
And we'll shout back that LF should take care of creating
appropriate tooling.
But shouting seems unlikely, I sent a patch to add Jeff K
and nobody batted an eyelid so far.
Send it for net, it's like a MAINTAINERS update.
next prev parent reply other threads:[~2024-03-13 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 12:07 [patch net-next] dpll: spec: use proper enum for pin capabilities attribute Jiri Pirko
2024-03-06 15:25 ` Jiri Pirko
2024-03-06 15:34 ` Jakub Kicinski
2024-03-13 14:26 ` Jakub Kicinski
2024-03-13 14:58 ` Jiri Pirko
2024-03-13 15:31 ` Jakub Kicinski [this message]
2024-03-14 8:42 ` Jiri Pirko
2024-03-07 4:27 ` Jakub Kicinski
2024-03-08 5:00 ` patchwork-bot+netdevbpf
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=20240313083111.4591590d@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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.