From: Eric Biggers <ebiggers@kernel.org>
To: "Peng.Zhou" <peng.zhou@mediatek.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Satya Tangirala <satyat@google.com>,
Chaotian Jing <chaotian.jing@mediatek.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Wulin Li <wulin.li@mediatek.com>
Subject: Re: [PATCH 1/4] mmc: mediatek: add Inline Crypto Engine support
Date: Fri, 5 Mar 2021 15:24:37 -0800 [thread overview]
Message-ID: <YEK9tXrOB2yQlqCl@gmail.com> (raw)
In-Reply-To: <1614947486.11643.4.camel@mbjsdccf07>
On Fri, Mar 05, 2021 at 08:31:26PM +0800, Peng.Zhou wrote:
> > > Somehow I can't apply this patch using git am. It looks like the mail
> > > isn't completely plain text (there's some html it seems), which may be
> > > why git am is complaining.
> >
> > I assume this is why patchwork didn't accept them. Please re-post in
> > plain/text and use "git send-email".
> >
> > Kind regards
> > Uffe
>
> I'm sorry about that, but I had used "git send-email" for above, and I
> had used checkpatch.pl to check but I don't find anything which will
> result in this error, I will check it much more...
>
Same problem with your v2 patches. Also I only received 2 of the 4 patches, and
none of them were received by the mailing list
(https://lkml.kernel.org/linux-mmc/).
Are you using something like 'git format-patch --cover-letter @~4..@'
and 'git send-email *.patch --to=... --cc=...'?
Otherwise, it might be a problem with the mail server you're using.
- Eric
prev parent reply other threads:[~2021-03-05 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210302024557.4868-1-peng.zhou@mediatek.com>
2021-03-02 5:33 ` [PATCH 1/4] mmc: mediatek: add Inline Crypto Engine support Satya Tangirala
2021-03-02 12:40 ` Ulf Hansson
[not found] ` <1614947486.11643.4.camel@mbjsdccf07>
2021-03-05 23:24 ` Eric Biggers [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=YEK9tXrOB2yQlqCl@gmail.com \
--to=ebiggers@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=chaotian.jing@mediatek.com \
--cc=linux-mmc@vger.kernel.org \
--cc=peng.zhou@mediatek.com \
--cc=satyat@google.com \
--cc=ulf.hansson@linaro.org \
--cc=wulin.li@mediatek.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