From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jamin Lin <jamin_lin@aspeedtech.com>
Cc: "Cédric Le Goater" <clg@kaod.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"Troy Lee" <troy_lee@aspeedtech.com>,
"Yunlin Tang" <yunlin.tang@aspeedtech.com>
Subject: Re: [PATCH v3 0/6] Support GPIO for AST2700
Date: Fri, 27 Sep 2024 10:18:33 -0400 [thread overview]
Message-ID: <20240927-nondescript-fat-ringtail-e13a10@lemur> (raw)
In-Reply-To: <SI2PR06MB5041632B8C7403F6B4B9D4F6FC6B2@SI2PR06MB5041.apcprd06.prod.outlook.com>
On Fri, Sep 27, 2024 at 06:29:22AM GMT, Jamin Lin wrote:
> > Also, your emails have an invalid "From" field set to
> > "qemu-devel@nongnu.org" when retrieved with the b4 command.
This is almost certainly done by the mailman list running on nongnu.org. It's
a very patch-hostile setting, so I'm surprised it's turned on at all.
> > I have been fixing them for a while. Could you please tell us how you send the
> > patchsets ?
> >
> >
> Command to send my patches as below.
> git send-email -cc jamin_lin@aspeedtech.com -cc troy_lee@aspeedtech.com -cc yunlin.tang@aspeedtech.com --to-cmd "./scripts/get_maintainer.pl ../v3-patch/*.patch" ../v3-patch/*.patch --no-smtp-auth
I suggest you generate your patches with --force-in-body-from (or set
format.forceInBodyFrom in your .git/config for that repository).
-K
next prev parent reply other threads:[~2024-09-27 14:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 7:45 [PATCH v3 0/6] Support GPIO for AST2700 Jamin Lin via
2024-09-26 7:45 ` [PATCH v3 1/6] hw/gpio/aspeed: Fix coding style Jamin Lin via
2024-09-26 16:08 ` Cédric Le Goater
2024-09-26 7:45 ` [PATCH v3 2/6] hw/gpio/aspeed: Support to set the different memory size Jamin Lin via
2024-09-26 16:08 ` Cédric Le Goater
2024-09-26 7:45 ` [PATCH v3 3/6] hw/gpio/aspeed: Support different memory region ops Jamin Lin via
2024-09-26 16:08 ` Cédric Le Goater
2024-09-26 7:45 ` [PATCH v3 4/6] hw/gpio/aspeed: Fix clear incorrect interrupt status for GPIO index mode Jamin Lin via
2024-09-27 2:12 ` Andrew Jeffery
2024-09-27 2:15 ` Jamin Lin
2024-09-26 7:45 ` [PATCH v3 5/6] hw/gpio/aspeed: Add AST2700 support Jamin Lin via
2024-09-27 2:19 ` Andrew Jeffery
2024-09-27 3:19 ` Jamin Lin
2024-09-26 7:45 ` [PATCH v3 6/6] aspeed/soc: Support GPIO for AST2700 Jamin Lin via
2024-09-26 16:10 ` Cédric Le Goater
2024-09-27 2:17 ` Jamin Lin
2024-09-26 16:12 ` [PATCH v3 0/6] " Cédric Le Goater
2024-09-27 2:16 ` Jamin Lin
2024-09-27 6:16 ` Cédric Le Goater
2024-09-27 6:29 ` Jamin Lin
2024-09-27 12:09 ` Cédric Le Goater
2024-09-27 14:18 ` Konstantin Ryabitsev [this message]
2024-09-30 6:00 ` Jamin Lin via
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=20240927-nondescript-fat-ringtail-e13a10@lemur \
--to=konstantin@linuxfoundation.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.com \
--cc=troy_lee@aspeedtech.com \
--cc=yunlin.tang@aspeedtech.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).