bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: "Björn Töpel" <bjorn.topel@intel.com>,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
	"Björn Töpel" <bjorn.topel@gmail.com>,
	"Maxim Mikityanskiy" <maximmi@mellanox.com>,
	maciej.fijalkowski@intel.com,
	"Alexei Starovoitov" <ast@kernel.org>,
	bpf@vger.kernel.org
Cc: netdev@vger.kernel.org,
	Magnus Karlsson <magnus.karlsson@intel.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Joe Perches <joe@perches.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust entry in XDP SOCKETS to actual file name
Date: Tue, 26 May 2020 00:23:07 +0200	[thread overview]
Message-ID: <22339b06-2cf1-0a3a-5813-86651ecd8d03@iogearbox.net> (raw)
In-Reply-To: <9d930e0e-5c77-11b8-6a8b-982fac711f6d@intel.com>

On 5/25/20 4:42 PM, Björn Töpel wrote:
> On 2020-05-25 16:15, Lukas Bulwahn wrote:
>> Commit 2b43470add8c ("xsk: Introduce AF_XDP buffer allocation API") added a
>> new header file include/net/xsk_buff_pool.h, but commit 28bee21dc04b
>> ("MAINTAINERS, xsk: Update AF_XDP section after moves/adds") added a file
>> entry referring to include/net/xsk_buffer_pool.h.
>>
>> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>>
>>    warning: no file matches  F:  include/net/xsk_buffer_pool.h
>>
>> Adjust the entry in XDP SOCKETS to the actual file name.
>>
>> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>> ---
>> Björn, please pick this minor non-urgent patch.
>>
>> applies to next-20200525 on top of the commits mentioned above
>>
> 
> Thanks Lukas!
> 
> Daniel/Alexei, this should go to the bpf-next tree.

Yep, applied, thanks!

      reply	other threads:[~2020-05-25 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 14:15 [PATCH] MAINTAINERS: adjust entry in XDP SOCKETS to actual file name Lukas Bulwahn
2020-05-25 14:42 ` Björn Töpel
2020-05-25 22:23   ` Daniel Borkmann [this message]

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=22339b06-2cf1-0a3a-5813-86651ecd8d03@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bjorn.topel@gmail.com \
    --cc=bjorn.topel@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=joe@perches.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=maximmi@mellanox.com \
    --cc=netdev@vger.kernel.org \
    /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).