From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: socket poll related cleanups v2
Date: Mon, 30 Jul 2018 09:13:04 -0700 (PDT) [thread overview]
Message-ID: <20180730.091304.333601798763006143.davem@davemloft.net> (raw)
In-Reply-To: <20180730074213.16832-1-hch@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Mon, 30 Jul 2018 09:42:09 +0200
> A couple of cleanups I stumbled upon when studying the networking
> poll code.
>
> Changes since v1:
> - drop a dispute patch from this series (to be sent separately)
Series applied, thanks!
next prev parent reply other threads:[~2018-07-30 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 7:42 Christoph Hellwig
2018-07-30 7:42 ` [PATCH 1/4] net: simplify sock_poll_wait Christoph Hellwig
2018-07-30 7:42 ` [PATCH 2/4] net: don not detour through struct sock to find the poll waitqueue Christoph Hellwig
2018-07-30 7:42 ` [PATCH 3/4] net: remove sock_poll_busy_loop Christoph Hellwig
2018-07-30 7:42 ` [PATCH 4/4] net: remove sock_poll_busy_flag Christoph Hellwig
2018-07-30 16:13 ` David Miller [this message]
2018-07-30 7:45 socket poll related cleanups v2 Christoph Hellwig
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=20180730.091304.333601798763006143.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--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
all inboxes | Powered by JetHome®