From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: YueHaibing <yuehaibing@huawei.com>, <linux@armlinux.org.uk>,
<fw@strlen.de>, <steffen.klassert@secunet.com>,
<davem@davemloft.net>, <ralf@linux-mips.org>,
<paul.burton@mips.com>
Cc: linux-s390@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-sh@vger.kernel.org, netdev@vger.kernel.org,
YueHaibing <yuehaibing@huawei.com>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next] defconfigs: remove obsolete CONFIG_INET_XFRM_MODE_* and CONFIG_INET6_XFRM_MODE_*
Date: Thu, 14 Nov 2019 20:07:36 +1100 (AEDT) [thread overview]
Message-ID: <47DFxN5pWqz9sP6@ozlabs.org> (raw)
In-Reply-To: <20190612071901.21736-1-yuehaibing@huawei.com>
On Wed, 2019-06-12 at 07:19:01 UTC, YueHaibing wrote:
> These Kconfig options has been removed in
> commit 4c145dce2601 ("xfrm: make xfrm modes builtin")
> So there is no point to keep it in defconfigs any longer.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/93a1544ad4ec4bd9147992e57b4f834ceb2cc159
cheers
next prev parent reply other threads:[~2019-11-14 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 7:19 [PATCH net-next] defconfigs: remove obsolete CONFIG_INET_XFRM_MODE_* and CONFIG_INET6_XFRM_MODE_* YueHaibing
2019-11-14 9:07 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-12 7:06 YueHaibing
2019-06-12 7:17 ` Yuehaibing
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=47DFxN5pWqz9sP6@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=steffen.klassert@secunet.com \
--cc=yuehaibing@huawei.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 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).