All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: Justin Chen <justin.chen@broadcom.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	bcm-kernel-feedback-list@broadcom.com,
	florian.fainelli@broadcom.com,
	Daniil Tatianin <d-tatianin@yandex-team.ru>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next] ethtool: ioctl: improve error checking for set_wol
Date: Thu, 1 Jun 2023 09:03:10 -0700	[thread overview]
Message-ID: <20230601090310.167e81b2@kernel.org> (raw)
In-Reply-To: <ZHi/aT6vxpdOryD8@corigine.com>

On Thu, 1 Jun 2023 17:55:21 +0200 Simon Horman wrote:
> + Daniil Tatianin <d-tatianin@yandex-team.ru>, Andrew Lunn <andrew@lunn.ch>
>   as per ./scripts/get_maintainer.pl --git-min-percent 25 net/ethtool/ioctl.c

Sorry to chime in but always prefer running get_maintainer on the patch
rather than a file path. File path misses stuff like Fixes tags.
If it was up to me that option would have been removed :(

  reply	other threads:[~2023-06-01 16:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 20:53 [PATCH net-next] ethtool: ioctl: improve error checking for set_wol Justin Chen
2023-06-01 15:55 ` Simon Horman
2023-06-01 16:03   ` Jakub Kicinski [this message]
2023-06-01 16:23     ` Simon Horman
2023-06-01 16:23     ` Justin Chen
2023-06-01 16:22   ` Justin Chen
2023-06-01 18:27     ` Justin Chen
2023-06-01 18:37       ` Florian Fainelli
2023-06-01 18:48         ` Andrew Lunn
2023-06-01 18:58           ` Justin Chen
2023-06-01 20:41             ` Woojung.Huh
2023-06-02  8:54     ` Simon Horman
2023-06-05 18:21 ` Jakub Kicinski
2023-06-05 18:46 Justin Chen
2023-06-07  3:54 ` Jakub Kicinski

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=20230601090310.167e81b2@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=d-tatianin@yandex-team.ru \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=justin.chen@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.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.