linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Christian Brauner <brauner@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v4 0/2] Fix libaio cancellation support
Date: Mon, 26 Feb 2024 12:50:46 -0800	[thread overview]
Message-ID: <9a0f534d-0251-492d-b7f9-30926e037c57@acm.org> (raw)
In-Reply-To: <20240221-hautnah-besonderen-e66d60bae4e6@brauner>

On 2/21/24 01:26, Christian Brauner wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs.misc
> 
> [1/2] fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio
>        https://git.kernel.org/vfs/vfs/c/34c6ea2e3aea
> [2/2] fs/aio: Make io_cancel() generate completions again
>        https://git.kernel.org/vfs/vfs/c/ee347c5af5be

Patch [1/2] ended up in Linus' tree as commit b820de741ae4, which is
great. However, I can't find patch [2/2] in any vfs branch nor in
linux-next. Did I perhaps overlook something?

$ git branch -r | grep vfs/ | while read b; do PAGER= git log 
--format=oneline origin/master..$b fs/aio.c; done
83c671617c943c7e369de96d95cc94739d42bcca eventfd: simplify eventfd_signal()
1c146b0406bddf3769705e4cd31a422a6564ab7b fs/aio: obey min_nr when doing 
wakeups
1808acc4fab22bed2f259dcdbc3138333caac676 eventfd: simplify eventfd_signal()
6e44f043186bf108c353353acc21adca4c3d73db fs: introduce fs_supers_lock

Thanks,

Bart.

  parent reply	other threads:[~2024-02-26 20:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 20:47 [PATCH v4 0/2] Fix libaio cancellation support Bart Van Assche
2024-02-15 20:47 ` [PATCH v4 1/2] fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio Bart Van Assche
2024-02-21 14:26   ` Jens Axboe
2024-02-21 15:32   ` (subset) " Christian Brauner
2024-03-04 19:10   ` Eric Biggers
2024-03-04 19:43     ` Bart Van Assche
2024-03-04 20:21       ` Jens Axboe
2024-03-05 20:43         ` Bart Van Assche
2024-03-05 21:55           ` Jens Axboe
2024-03-04 20:09     ` Jens Axboe
2024-03-04 20:49       ` Eric Biggers
2024-03-04 20:53         ` Jens Axboe
2024-02-15 20:47 ` [PATCH v4 2/2] fs/aio: Make io_cancel() generate completions again Bart Van Assche
2024-02-16  7:13   ` Christoph Hellwig
2024-02-16 12:08     ` Christian Brauner
2024-02-16 17:11     ` Bart Van Assche
2024-02-27  8:55   ` (subset) " Christian Brauner
2024-02-21  9:26 ` [PATCH v4 0/2] Fix libaio cancellation support Christian Brauner
2024-02-21 17:39   ` Bart Van Assche
2024-02-26 20:50   ` Bart Van Assche [this message]
2024-02-27  8:55     ` Christian Brauner
2024-03-04 18:53 ` Eric Biggers

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=9a0f534d-0251-492d-b7f9-30926e037c57@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).