All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Lee <hburaylee@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: phillip@squashfs.org.uk, squashfs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] squashfs: fix inode number description in documentation
Date: Sun, 13 Sep 2026 21:01:24 +0800	[thread overview]
Message-ID: <20260913210124.0000628d@gmail.com> (raw)
In-Reply-To: <20260910-bedrucken-wipfel-beraten-dca08f04b19c@brauner>

On Thu, 10 Sep 2026 10:12:45 +0200
Christian Brauner <brauner@kernel.org> wrote:

> On Tue, 08 Sep 2026 21:01:03 +0800, Ray Lee wrote:
> > squashfs: fix inode number description in documentation  
> 
> Applied to the vfs-7.4.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-7.4.misc branch should appear in linux-next soon.
> 
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
> 
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be
> updated.
> 
> Note that commit hashes shown below are subject to change due to
> rebase, trailer updates or similar. If in doubt, please check the
> listed branch.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-7.4.misc
> 
> [1/1] squashfs: fix inode number description in documentation
>       https://git.kernel.org/vfs/vfs/c/bfe240aab4a1
> 

Thanks for applying!

      reply	other threads:[~2026-09-13 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 13:01 [PATCH] squashfs: fix inode number description in documentation Ray Lee
2026-09-10  8:12 ` Christian Brauner
2026-09-13 13:01   ` Ray Lee [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=20260913210124.0000628d@gmail.com \
    --to=hburaylee@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=phillip@squashfs.org.uk \
    --cc=squashfs-devel@lists.sourceforge.net \
    /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.