From: Christoph Hellwig <hch@lst.de>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-aio@kvack.org, Avi Kivity <avi@scylladb.com>,
linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/6] add test for aio poll and io_pgetevents
Date: Thu, 4 Jan 2018 11:29:53 +0100 [thread overview]
Message-ID: <20180104102953.GA5021@lst.de> (raw)
In-Reply-To: <CAOFm3uGeefVs1RBx0zJeQR5cXYvun9OxyUddzevqeDyX_MHyRg@mail.gmail.com>
On Thu, Jan 04, 2018 at 11:24:16AM +0100, Philippe Ombredanne wrote:
> Would you consider using an SPDX tag instead as documented in Thomas
> doc patches [1]? This rather close to what you use today and would
> come out as this, on the first line:
>
> SPDX-License-Identifier: LGPL-2.1+
>
> Thank you!
Only if the libaio maintainers do the work of actually explaning what
such tags mean in their project, because without that it would be
entirely meaningless.
next prev parent reply other threads:[~2018-01-04 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 8:03 libaio: resurrect aio poll and add io_pgetevents support Christoph Hellwig
2018-01-04 8:03 ` [PATCH 1/6] resurrect aio poll support Christoph Hellwig
2018-01-04 8:03 ` [PATCH 2/6] move _body_io_syscall to the generic syscall.h Christoph Hellwig
2018-01-05 16:25 ` Jeff Moyer
2018-01-05 16:40 ` Benjamin LaHaise
2018-01-05 22:49 ` Jeff Moyer
2018-01-04 8:03 ` [PATCH 3/6] provide a generic io_syscall6 Christoph Hellwig
2018-01-04 8:03 ` [PATCH 4/6] move the aio_ring defintion and empty check into a header Christoph Hellwig
2018-01-04 8:03 ` [PATCH 5/6] add support for io_pgetevents Christoph Hellwig
2018-01-04 8:03 ` [PATCH 6/6] add test for aio poll and io_pgetevents Christoph Hellwig
2018-01-04 10:24 ` Philippe Ombredanne
2018-01-04 10:29 ` Christoph Hellwig [this message]
2018-01-05 22:55 ` Jeff Moyer
2018-01-05 22:57 ` libaio: resurrect aio poll and add io_pgetevents support Jeff Moyer
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=20180104102953.GA5021@lst.de \
--to=hch@lst.de \
--cc=avi@scylladb.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pombredanne@nexb.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