From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: 徐傑生 <jasonhell19@gmail.com>
Cc: yang.chen@quantatw.com, jerry.lin@quantatw.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, joel@jms.id.au,
patrick@stwcx.xyz, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add Meta(Facebook) Ventura BMC(AST2600)
Date: Thu, 24 Oct 2024 10:48:22 +1030 [thread overview]
Message-ID: <32cb6d9388fb136f7cd7ad1ab0d60d83ae387982.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAFGtgY3BJcpC=Q0cYZQa01D5BFAQTt6GEr=0_mrPGUntHYVioA@mail.gmail.com>
On Wed, 2024-10-23 at 16:32 +0800, 徐傑生 wrote:
> Andrew Jeffery <andrew@codeconstruct.com.au> 於 2024年10月23日 週三 下午2:15寫道:
> >
> > On Tue, 2024-10-22 at 10:12 +0800, Jason-Hsu wrote:
> > > Add Linux device tree entry related to Meta(Facebook) Ventura specific
> > > devices connected to BMC(AST2600) SoC.
> > >
> > > Signed-off-by: Jason-Hsu <jasonhell19@gmail.com>
> >
> > What commands are you running to generate and send your patch series?
> >
> > The patches must be threaded properly.
> >
> > `git send-email` or `b4` both do what is expected without any effort
> > required. Please consider using them, particularly b4, if you're not
> > already.
> >
> > Andrew
>
> We use `git format-patch` and `git send-email` command to generate and
> send patch series as below, could you help to check? Thank you.
>
> git format-patch -2 --cover-letter
>
> git send-email --smtp-debug --to=robh@kernel.org
> --to=krzk+dt@kernel.org --to=conor+dt@kernel.org --to=joel@jms.id.au
> --to=andrew@codeconstruct.com.au --to=patrick@stwcx.xyz
> --to=devicetree@vger.kernel.org
> --to=linux-arm-kernel@lists.infradead.org
> --to=linux-aspeed@lists.ozlabs.org --to=linux-kernel@vger.kernel.org
> --cc=yang.chen@quantatw.com --cc=jerry.lin@quantatw.com *.patch
>
So from the details in the cover letter I'm guessing that you're using
Ubuntu 22.04 LTS (Jammy). At least, Jammy ships git-2.34.1, which is
what is mentioned in the cover letter.
The --thread option in the man-page for git-format-patch[1] says:
The default is --no-thread, unless the format.thread configuration is
set. If --thread is specified without a style, it defaults to the style
specified by format.thread if any, or else shallow.
Beware that the default for git send-email is to thread emails itself.
If you want git format-patch to take care of threading, you will want
to ensure that threading is disabled for git send-email.
[1]: https://manpages.ubuntu.com/manpages/jammy/en/man1/git-format-patch.1.html
The --thread option in the man-page for git-send-email[2] says:
If disabled with "--no-thread", those headers will not be added (unless
specified with --in-reply-to). Default is the value of the
sendemail.thread configuration value; if that is unspecified, default
to --thread.
[2]: https://manpages.ubuntu.com/manpages/jammy/en/man1/git-send-email.1.html
Since you're not supplying any thread-related arguments in either case,
I wonder if you have thread values set in your git config. What's the
output of the following two commands for you?
$ git config --show-scope --get format.thread
$ git config --show-scope --get sendemail.thread
Regardless, you may want to try passing `--thread` in your `git send-
email` invocation.
Finally, please pass `-v $X` to `git format-patch` to version your
series (the value for X is how many times you've sent revisions of the
series). Currently I count 3 distinct attempts, so next time you send
out the patches you should pass `-v 4`. However, the b4 tool is helpful
here, as it largely automates the process for you.
Andrew
prev parent reply other threads:[~2024-10-24 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 2:12 [PATCH 0/2] Add Meta(Facebook) Ventura BMC(AST2600) Jason-Hsu
2024-10-23 6:14 ` Andrew Jeffery
2024-10-23 8:32 ` 徐傑生
2024-10-24 0:18 ` Andrew Jeffery [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=32cb6d9388fb136f7cd7ad1ab0d60d83ae387982.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jasonhell19@gmail.com \
--cc=jerry.lin@quantatw.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=robh@kernel.org \
--cc=yang.chen@quantatw.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 NNTP newsgroup(s).