From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: kuba@kernel.org, ccaulfie@redhat.com, teigland@redhat.com,
vyasevich@gmail.com, nhorman@tuxdriver.com,
marcelo.leitner@gmail.com, linux-kernel@vger.kernel.org,
cluster-devel@redhat.com, netdev@vger.kernel.org
Subject: Re: remove kernel_getsockopt
Date: Wed, 27 May 2020 15:11:46 -0700 (PDT) [thread overview]
Message-ID: <20200527.151146.209703742963070529.davem@davemloft.net> (raw)
In-Reply-To: <20200527182229.517794-1-hch@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Wed, 27 May 2020 20:22:27 +0200
> this series reduces scope from the last round and just removes
> kernel_getsockopt to avoid conflicting with the sctp cleanup series.
Series applied to net-next, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] remove kernel_getsockopt
Date: Wed, 27 May 2020 15:11:46 -0700 (PDT) [thread overview]
Message-ID: <20200527.151146.209703742963070529.davem@davemloft.net> (raw)
In-Reply-To: <20200527182229.517794-1-hch@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Wed, 27 May 2020 20:22:27 +0200
> this series reduces scope from the last round and just removes
> kernel_getsockopt to avoid conflicting with the sctp cleanup series.
Series applied to net-next, thanks.
next prev parent reply other threads:[~2020-05-27 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:22 remove kernel_getsockopt Christoph Hellwig
2020-05-27 18:22 ` [Cluster-devel] " Christoph Hellwig
2020-05-27 18:22 ` [PATCH 1/2] dlm: use the tcp version of accept_from_sock for sctp as well Christoph Hellwig
2020-05-27 18:22 ` [Cluster-devel] " Christoph Hellwig
2020-05-27 18:22 ` [PATCH 2/2] net: remove kernel_getsockopt Christoph Hellwig
2020-05-27 18:22 ` [Cluster-devel] " Christoph Hellwig
2020-05-27 22:11 ` David Miller [this message]
2020-05-27 22:11 ` [Cluster-devel] " David Miller
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=20200527.151146.209703742963070529.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ccaulfie@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=teigland@redhat.com \
--cc=vyasevich@gmail.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.