From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"slava@dubeyko.com" <slava@dubeyko.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: [PATCH 1/2] hfsplus: fix to update ctime after rename
Date: Thu, 01 May 2025 21:10:57 +0200 [thread overview]
Message-ID: <082cd97a11ca1680249852e975f8c3e06b53c26c.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <b0181fae61173d3d463637c7f2b197a4befc4796.camel@ibm.com>
Hi Slava,
On Thu, 2025-05-01 at 18:57 +0000, Viacheslav Dubeyko wrote:
> On Thu, 2025-05-01 at 12:01 +0000, 李扬韬 wrote:
> > Hi Slava,
> >
> > > Unfortunately, I am unable to apply you patch. In 6.15-rc4 we have already:
> >
> > Why can't apply?
> >
> > > Could you please prepare the patch for latest state of the kernel tree?
> >
> > In fact, I applied these two patches to 6.15-rc4, and there were no abnormalities.
> > based on commit 4f79eaa2ceac86a0e0f304b0bab556cca5bf4f30
> >
>
> It's strange. The 'git apply' doesn't work, but 'git am' does work.
>
> git apply -v ./\[EXTERNAL\]\ \[PATCH\ 1_2\]\ hfsplus\:\ fix\ to\ update\ ctime\
> after\ rename.mbox
> Checking patch fs/hfsplus/dir.c...
> error: while searching for:
> struct inode *new_dir, struct dentry *new_dentry,?
> unsigned int flags)?
> {?
> int res;?
> ?
> if (flags & ~RENAME_NOREPLACE)?
>
> error: patch failed: fs/hfsplus/dir.c:534
> error: fs/hfsplus/dir.c: patch does not apply
>
> git am ./\[EXTERNAL\]\ \[PATCH\ 1_2\]\ hfsplus\:\ fix\ to\ update\ ctime\ after\
> rename.mbox
> Applying: hfsplus: fix to update ctime after rename
>
> Does 'git apply' works on your side if you try to apply the patch from email? Is
> it some glitch on my side? As far as I can see, I am trying to apply on clean
> kernel tree.
git-apply is for applying plain patches while git-am is for patches from mailboxes.
I would suggest to always use git-am after fetching patches using "b4 am <MSGID>"
from the kernel mailing list.
Please note that when you apply patches with git-am, you should always use the "-s"
option so that the patches are automatically signed-off with your own email address.
Btw, can you push your tree somewhere until you've got your kernel.org account?
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2025-05-01 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 20:15 Yangtao Li
2025-04-29 20:15 ` [PATCH 2/2] hfs: " Yangtao Li
2025-04-29 21:31 ` Viacheslav Dubeyko
2025-05-02 0:03 ` Viacheslav Dubeyko
2025-05-07 14:22 ` 回复: " 李扬韬
2025-05-09 17:51 ` Viacheslav Dubeyko
2025-05-09 19:02 ` Viacheslav Dubeyko
2025-05-10 5:31 ` 回复: " 李扬韬
2025-05-15 1:10 ` Viacheslav Dubeyko
2025-04-29 21:27 ` [PATCH 1/2] hfsplus: " Viacheslav Dubeyko
2025-05-01 12:01 ` 回复: " 李扬韬
2025-05-01 18:57 ` Viacheslav Dubeyko
2025-05-01 19:10 ` John Paul Adrian Glaubitz [this message]
2025-05-01 19:48 ` Viacheslav Dubeyko
2025-05-02 12:52 ` Theodore Ts'o
2025-05-05 22:31 ` Viacheslav Dubeyko
2025-05-02 0:07 ` 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=082cd97a11ca1680249852e975f8c3e06b53c26c.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=Slava.Dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.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®