From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
frank.li@vivo.com, jkoolstra@xs4all.nl,
mehdi.benhadjkhelifa@gmail.com, shardul.b@mpiricsoftware.com,
torvalds@linux-foundation.org
Subject: Re: [GIT PULL] hfs/hfsplus changes for 7.0-rc1
Date: Sat, 07 Feb 2026 09:55:01 +0100 [thread overview]
Message-ID: <66af2e9a17dab9f1ef79ad5812ec91aa9c0be005.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <a1602ccf-73ce-46a3-b2f9-76cc7d2401e3@I-love.SAKURA.ne.jp>
Hi Tetsuo,
On Sat, 2026-02-07 at 10:18 +0900, Tetsuo Handa wrote:
> On 2026/02/07 9:26, Viacheslav Dubeyko wrote:
> > Hello Linus,
> >
> > This pull request contains several fixes of syzbot reported
> > issues and HFS+ fixes of xfstests failures.
>
> Where is the flow for testing these patches in linux-next tree?
> Are HFS/HFS+ patches directly going to linux tree without testing
> in linux-next tree?
The HFS/HFS+ tree should be part of linux-next which is why it's got
a branch named like this [1].
Adrian
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git/log/?h=for-next
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-02-07 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 0:26 Viacheslav Dubeyko
2026-02-07 1:18 ` Tetsuo Handa
2026-02-07 8:55 ` John Paul Adrian Glaubitz [this message]
2026-02-07 9:44 ` Tetsuo Handa
2026-02-10 0:50 ` pr-tracker-bot
2026-02-10 11:12 ` Tetsuo Handa
2026-02-10 18:11 ` Viacheslav Dubeyko
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=66af2e9a17dab9f1ef79ad5812ec91aa9c0be005.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=frank.li@vivo.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mehdi.benhadjkhelifa@gmail.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=shardul.b@mpiricsoftware.com \
--cc=slava@dubeyko.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®