mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Guikun Yang <yangguikun19@qq.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] qnx6: validate di_filelevels against the block size
Date: Tue, 17 Nov 2026 14:49:49 +0100	[thread overview]
Message-ID: <20261117-anheben-kauen-botschaft-efbcb6e18d72@brauner> (raw)
In-Reply-To: <tencent_BB8BEFED1159A70D5381A81D1F8EA88BD407@qq.com>

On Sun, Nov 08, 2026 at 10:01:00AM +0800, Guikun Yang wrote:
> diff --git a/fs/qnx6/inode.c b/fs/qnx6/inode.c
> index 1111111..2222222 100644
> --- a/fs/qnx6/inode.c
> +++ b/fs/qnx6/inode.c

Same as your ufs patch: this diff was never produced by git. The index
line is made up, the second hunk header doesn't match its hunk, and the
Fixes: tag sits below the diff. It doesn't apply.

I'm not going to fix up hand-written or generated diffs. Generate
patches with git format-patch from a tree you actually built and tested
the change in, and send them with git send-email. Anything else won't
be applied.

      reply	other threads:[~2026-11-17 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c4-qnx6-filelevels-ubsan-20261031@qq.com>
2026-11-08  2:01 ` Guikun Yang
2026-11-17 13:49   ` Christian Brauner [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=20261117-anheben-kauen-botschaft-efbcb6e18d72@brauner \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yangguikun19@qq.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

all inboxes | Powered by JetHome®