From: Andrey Albershteyn <aalbersh@redhat.com>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: dchinner@redhat.com, djwong@kernel.org, hch@lst.de,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
mark.tinguely@oracle.com
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to f2e812c1522d
Date: Tue, 26 Mar 2024 16:10:18 +0100 [thread overview]
Message-ID: <dlmrrqswfhspcjn6ai7jfh54t4mwrgus2ex3b4klpcbszq72zw@cizkdcybodfs> (raw)
In-Reply-To: <87r0fxgmmj.fsf@debian-BULLSEYE-live-builder-AMD64>
On 2024-03-26 18:42:47, Chandan Babu R wrote:
> On Tue, Mar 26, 2024 at 12:14:07 PM +0100, Andrey Albershteyn wrote:
> > On 2024-03-26 12:10:53, Andrey Albershteyn wrote:
> >> On 2024-03-26 15:28:01, Chandan Babu R wrote:
> >> > Hi folks,
> >> >
> >> > The for-next branch of the xfs-linux repository at:
> >> >
> >> > https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> >> >
> >> > has just been updated.
> >> >
> >> > Patches often get missed, so please check if your outstanding patches
> >> > were in this update. If they have not been in this update, please
> >> > resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
> >> > the next update.
> >> >
> >> > The new head of the for-next branch is commit:
> >> >
> >> > f2e812c1522d xfs: don't use current->journal_info
> >> >
> >> > 2 new commits:
> >> >
> >> > Dave Chinner (2):
> >> > [15922f5dbf51] xfs: allow sunit mount option to repair bad primary sb stripe values
> >> > [f2e812c1522d] xfs: don't use current->journal_info
> >> >
> >> > Code Diffstat:
> >> >
> >> > fs/xfs/libxfs/xfs_sb.c | 40 +++++++++++++++++++++++++++--------
> >> > fs/xfs/libxfs/xfs_sb.h | 5 +++--
> >> > fs/xfs/scrub/common.c | 4 +---
> >> > fs/xfs/xfs_aops.c | 7 ------
> >> > fs/xfs/xfs_icache.c | 8 ++++---
> >> > fs/xfs/xfs_trans.h | 9 +-------
> >> > 6 files changed, 41 insertions(+), 32 deletions(-)
> >> >
> >>
> >> I think [1] is missing
> >>
> >> [1]: https://lore.kernel.org/linux-xfs/20240314170700.352845-3-aalbersh@redhat.com/
>
> I am sorry to have missed that patch.
>
> >
> > Should I resend it?
>
> You don't have to resend it.
>
> I will include the above patch in 6.9-rc3 fixes queue.
>
> --
> Chandan
>
Thanks!
--
- Andrey
prev parent reply other threads:[~2024-03-26 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 9:58 [ANNOUNCE] xfs-linux: for-next updated to f2e812c1522d Chandan Babu R
2024-03-26 11:10 ` Andrey Albershteyn
2024-03-26 11:14 ` Andrey Albershteyn
2024-03-26 13:12 ` Chandan Babu R
2024-03-26 15:10 ` Andrey Albershteyn [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=dlmrrqswfhspcjn6ai7jfh54t4mwrgus2ex3b4klpcbszq72zw@cizkdcybodfs \
--to=aalbersh@redhat.com \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mark.tinguely@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).