From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-next@vger.kernel.org, linux-block@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v5 0/8] make statx() return DIO alignment information
Date: Tue, 18 Oct 2022 15:55:24 +1100 [thread overview]
Message-ID: <20221018155524.5fc4e421@canb.auug.org.au> (raw)
In-Reply-To: <20220913063025.4815466c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi Eric,
On Tue, 13 Sep 2022 06:30:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Sun, 11 Sep 2022 19:54:12 -0500 Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > Stephen, can you add my git branch for this patchset to linux-next?
> >
> > URL: https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
> > Branch: statx-dioalign
> >
> > This is targeting the 6.1 merge window with a pull request to Linus.
>
> Added from today.
I notice that this branch has been removed. Are you finished with it
(i.e. should I remove it from linux-next)?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-18 4:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 6:58 [PATCH v5 0/8] make statx() return DIO alignment information Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-27 6:58 ` [PATCH v5 1/8] statx: add direct I/O " Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-09-07 9:10 ` Christian Brauner
2022-09-07 9:10 ` [f2fs-dev] " Christian Brauner
2022-08-27 6:58 ` [PATCH v5 2/8] vfs: support STATX_DIOALIGN on block devices Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-09-06 8:10 ` Christoph Hellwig
2022-09-06 8:10 ` [f2fs-dev] " Christoph Hellwig
2022-09-07 9:09 ` Christian Brauner
2022-09-07 9:09 ` [f2fs-dev] " Christian Brauner
2022-08-27 6:58 ` [PATCH v5 3/8] fscrypt: change fscrypt_dio_supported() to prepare for STATX_DIOALIGN Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-27 6:58 ` [PATCH v5 4/8] ext4: support STATX_DIOALIGN Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-27 6:58 ` [PATCH v5 5/8] f2fs: move f2fs_force_buffered_io() into file.c Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-29 17:37 ` Jaegeuk Kim
2022-08-29 17:37 ` [f2fs-dev] " Jaegeuk Kim
2022-08-27 6:58 ` [PATCH v5 6/8] f2fs: simplify f2fs_force_buffered_io() Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-29 17:36 ` Jaegeuk Kim
2022-08-29 17:36 ` [f2fs-dev] " Jaegeuk Kim
2022-08-27 6:58 ` [PATCH v5 7/8] f2fs: support STATX_DIOALIGN Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-29 17:43 ` Jaegeuk Kim
2022-08-29 17:43 ` [f2fs-dev] " Jaegeuk Kim
2022-08-27 6:58 ` [PATCH v5 8/8] xfs: " Eric Biggers
2022-08-27 6:58 ` [f2fs-dev] " Eric Biggers
2022-08-27 15:34 ` Darrick J. Wong
2022-08-27 15:34 ` [f2fs-dev] " Darrick J. Wong
2022-09-06 8:11 ` Christoph Hellwig
2022-09-06 8:11 ` [f2fs-dev] " Christoph Hellwig
2022-09-06 22:08 ` [PATCH v5 0/8] make statx() return DIO alignment information Eric Biggers
2022-09-06 22:08 ` [f2fs-dev] " Eric Biggers
2022-09-12 0:54 ` Eric Biggers
2022-09-12 0:54 ` [f2fs-dev] " Eric Biggers
2022-09-12 20:30 ` Stephen Rothwell
2022-10-18 4:55 ` Stephen Rothwell [this message]
2022-10-18 7:07 ` Eric Biggers
2022-10-18 7:07 ` [f2fs-dev] " Eric Biggers
2022-10-18 20:08 ` Stephen Rothwell
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=20221018155524.5fc4e421@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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 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.