All of lore.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: Wed, 13 Mar 2024 15:58:19 +0100	[thread overview]
Message-ID: <ZfG_C6wi4EeBj9l3@nanopsycho> (raw)
In-Reply-To: <20240313072608.1dc45382@kernel.org>

Wed, Mar 13, 2024 at 03:26:08PM CET, kuba@kernel.org wrote:
>On Wed, 6 Mar 2024 07:34:19 -0800 Jakub Kicinski wrote:
>> > Note that netdev/cc_maintainers fails as I didn't cc michal.michalik@intel.com
>> > on purpose, as the address bounces.
>> > 
>> > Btw, do we have a way to ignore such ccs? .get_maintainer.ignore looks
>> > like a good candidate, but is it okay to put closed emails there?  
>> 
>> Oh, great, I wasn't aware of this.
>> 
>> 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...


  reply	other threads:[~2024-03-13 14:58 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 [this message]
2024-03-13 15:31         ` Jakub Kicinski
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=ZfG_C6wi4EeBj9l3@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 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.