public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
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: Thu, 14 Mar 2024 09:42:53 +0100	[thread overview]
Message-ID: <ZfK4jdJCyVzKLTq4@nanopsycho> (raw)
In-Reply-To: <20240313083111.4591590d@kernel.org>

Wed, Mar 13, 2024 at 04:31:11PM CET, kuba@kernel.org wrote:
>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.

Interesting, his email gets no longer returned by get_maintainers.
perhaps there is some timeout there (I was looking but got a bit
Perlsick :)

  reply	other threads:[~2024-03-14  8:42 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
2024-03-14  8:42           ` Jiri Pirko [this message]
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=ZfK4jdJCyVzKLTq4@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox