From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
adrian@lisas.de, smueller@chronox.de, avagin@virtuozzo.com
Subject: Re: [PATCH] aio: don't expose __aio_sigset in uapi
Date: Wed, 18 Jul 2018 04:26:18 +0100 [thread overview]
Message-ID: <20180718032618.GP30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180717151017.GA22533@lst.de>
On Tue, Jul 17, 2018 at 05:10:17PM +0200, Christoph Hellwig wrote:
> Al, can you send this to Linus for the next 4.18-rc?
Applied.
prev parent reply other threads:[~2018-07-18 4:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 13:48 [PATCH] aio: don't expose __aio_sigset in uapi Christoph Hellwig
2018-07-11 14:22 ` Adrian Reber
2018-07-17 15:10 ` Christoph Hellwig
2018-07-18 3:26 ` Al Viro [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=20180718032618.GP30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adrian@lisas.de \
--cc=avagin@virtuozzo.com \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smueller@chronox.de \
/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).