From: Greg KH <gregkh@linuxfoundation.org>
To: Pan Zhang <zhangpan26@huawei.com>
Cc: hushiyuan@huawei.com, ulf.hansson@linaro.org,
allison@lohutok.net, tglx@linutronix.de,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: host: use kzalloc instead of kmalloc and memset
Date: Tue, 17 Dec 2019 08:32:22 +0100 [thread overview]
Message-ID: <20191217073222.GA2472756@kroah.com> (raw)
In-Reply-To: <1576566037-29837-1-git-send-email-zhangpan26@huawei.com>
On Tue, Dec 17, 2019 at 03:00:37PM +0800, Pan Zhang wrote:
> Signed-off-by: Pan Zhang <zhangpan26@huawei.com>
> ---
> drivers/mmc/host/vub300.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
I know I can not take patches without any changelog text, hopefully
other maintainers also do the same.
Please fix,
greg k-h
prev parent reply other threads:[~2019-12-17 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 7:00 [PATCH] mmc: host: use kzalloc instead of kmalloc and memset Pan Zhang
2019-12-17 7:32 ` Greg KH [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=20191217073222.GA2472756@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=allison@lohutok.net \
--cc=hushiyuan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=zhangpan26@huawei.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).