netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Tobias Klauser <tklauser@distanz.ch>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next] indirect_call_wrapper: Fix typo in INDIRECT_CALL_$NR kerneldoc
Date: Mon, 20 Nov 2023 09:24:14 +0000	[thread overview]
Message-ID: <20231120092414.GJ186930@vergenet.net> (raw)
In-Reply-To: <20231116010310.4664dd38@kernel.org>

On Thu, Nov 16, 2023 at 01:03:10AM -0500, Jakub Kicinski wrote:
> On Wed, 15 Nov 2023 17:56:26 +0000 Simon Horman wrote:
> > To the netdev maintainers: get_maintainer.pl doesn't seem to
> > know much about include/linux/indirect_call_wrapper.h.
> > Should that be fixed?
> 
> I'm curious how many of such files exist under include/linux.
> Files which are not really networking specific but only tree
> the changes ever went thru is netdev.. 
> But yes, in the interest of "taking responsibility" we should
> probably claim it.

Thanks, patch sent.

Link: https://lore.kernel.org/netdev/20231120-indirect_call_wrapper-maintainer-v1-1-0a6bb1f7363e@kernel.org/

  reply	other threads:[~2023-11-20  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 10:42 [PATCH net-next] indirect_call_wrapper: Fix typo in INDIRECT_CALL_$NR kerneldoc Tobias Klauser
2023-11-15 17:56 ` Simon Horman
2023-11-16  6:03   ` Jakub Kicinski
2023-11-20  9:24     ` Simon Horman [this message]
2023-11-16 12:10 ` 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=20231120092414.GJ186930@vergenet.net \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tklauser@distanz.ch \
    /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;
as well as URLs for NNTP newsgroup(s).