From: Eric Biggers <ebiggers@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
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 00:07:57 -0700 [thread overview]
Message-ID: <Y05QzQM2ed8sOJxC@sol.localdomain> (raw)
In-Reply-To: <20221018155524.5fc4e421@canb.auug.org.au>
On Tue, Oct 18, 2022 at 03:55:24PM +1100, Stephen Rothwell wrote:
> 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)?
>
Yes, I think so. This patchset has been merged upstream. Any more patches
related to STATX_DIOALIGN should go in through the VFS or filesystem-specific
trees.
- Eric
next prev parent reply other threads:[~2022-10-18 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220827065851.135710-1-ebiggers@kernel.org>
[not found] ` <YxfE8zjqkT6Zn+Vn@quark>
2022-09-12 0:54 ` [PATCH v5 0/8] make statx() return DIO alignment information Eric Biggers
2022-09-12 20:30 ` Stephen Rothwell
2022-10-18 4:55 ` Stephen Rothwell
2022-10-18 7:07 ` Eric Biggers [this message]
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=Y05QzQM2ed8sOJxC@sol.localdomain \
--to=ebiggers@kernel$(echo .)org \
--cc=kbusch@kernel$(echo .)org \
--cc=linux-api@vger$(echo .)kernel.org \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-ext4@vger$(echo .)kernel.org \
--cc=linux-f2fs-devel@lists$(echo .)sourceforge.net \
--cc=linux-fscrypt@vger$(echo .)kernel.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-xfs@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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