From: Markus Elfring <Markus.Elfring@web.de>
To: yanxiaoyong5@gmail.com, linux-mmc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Avri Altman <avri.altman@wdc.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Raul E Rangel <rrangel@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc/core: Avoid oops in mmc_sd_runtime_resume()
Date: Fri, 1 May 2020 20:50:26 +0200 [thread overview]
Message-ID: <2085b083-42f0-5aaf-9810-f73195fa579c@web.de> (raw)
Please send a patch with a corrected commit message.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=052c467cb58748e302a95546925928e637025acc#n102
1. The patch subject was not succinct.
2. The change description was missing.
3. The real name is expected for the signature.
Regards,
Markus
reply other threads:[~2020-05-01 18:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2085b083-42f0-5aaf-9810-f73195fa579c@web.de \
--to=markus.elfring@web.de \
--cc=avri.altman@wdc.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rrangel@chromium.org \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=yanxiaoyong5@gmail.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).