Netdev List
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Joe Perches <joe@perches.com>
Cc: <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	<netdev@vger.kernel.org>, "Florian Westphal" <fw@strlen.de>
Subject: Re: Bad MAINTAINERS pattern in section 'NETWORKING [IPSEC]'
Date: Thu, 4 Oct 2018 07:28:45 +0200	[thread overview]
Message-ID: <20181004052845.GG3823@gauss3.secunet.de> (raw)
In-Reply-To: <20180928220123.30999-1-joe@perches.com>

On Fri, Sep 28, 2018 at 03:01:23PM -0700, Joe Perches wrote:
> Please fix this defect appropriately.
> 
> linux-next MAINTAINERS section:
> 
> 	10233	NETWORKING [IPSEC]
> 	10234	M:	Steffen Klassert <steffen.klassert@secunet.com>
> 	10235	M:	Herbert Xu <herbert@gondor.apana.org.au>
> 	10236	M:	"David S. Miller" <davem@davemloft.net>
> 	10237	L:	netdev@vger.kernel.org
> 	10238	T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
> 	10239	T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
> 	10240	S:	Maintained
> -->	10241	F:	net/core/flow.c

This file went away with the flowcache removal.
I plan to apply the patch below to the ipsec tree:

Subject: [PATCH] MAINTAINERS: Remove net/core/flow.c

net/core/flow.c does not exist anymore, so remove it
from the IPSEC NETWORKING section of the MAINTAINERS
file.

Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index dcb0191c4f54..4ff21dac9b45 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10130,7 +10130,6 @@ L:	netdev@vger.kernel.org
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
 S:	Maintained
-F:	net/core/flow.c
 F:	net/xfrm/
 F:	net/key/
 F:	net/ipv4/xfrm*
-- 
2.17.1

      reply	other threads:[~2018-10-04  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 22:01 Bad MAINTAINERS pattern in section 'NETWORKING [IPSEC]' Joe Perches
2018-10-04  5:28 ` Steffen Klassert [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=20181004052845.GG3823@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --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