From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: unSimple <unsimple1993@163.com>
Cc: <tsbogend@alpha.franken.de>, <linux-kernel@vger.kernel.org>,
<linux-mips@vger.kernel.org>, <ralf@linux-mips.org>
Subject: Re: [PATCH v1] MIPS: ip22-gio: Add check for the return value of kzalloc()
Date: Fri, 1 Apr 2022 12:09:57 +0300 [thread overview]
Message-ID: <4eb43887-44a4-4693-8488-4847d80b6bd8@omp.ru> (raw)
In-Reply-To: <16aa9238.4bf6.17fd8fe37ad.Coremail.unsimple1993@163.com>
On 3/30/22 7:03 AM, unSimple wrote:
> OK, here is the new version.
That won't do, your original patch description should be here.
And it should be a fresh posting with [PATCH v2] in the subject.
> Signed-off-by: QintaoShen <unSimple1993@163.com>
> ---
You need to describe what changes between v1 and v2 here...
> arch/mips/sgi-ip22/ip22-gio.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/mips/sgi-ip22/ip22-gio.c b/arch/mips/sgi-ip22/ip22-gio.c
> index dfc52f6..f94f58b 100644
> --- a/arch/mips/sgi-ip22/ip22-gio.c
> +++ b/arch/mips/sgi-ip22/ip22-gio.c
> @@ -363,6 +363,10 @@ static void ip22_check_gio(int slotno, unsigned long addr, int irq)
> printk(KERN_INFO "GIO: slot %d : %s (id %x)\n",
> slotno, name, id);
> gio_dev = kzalloc(sizeof *gio_dev, GFP_KERNEL);
> +
No need for empty line here.
> +if (!gio_dev)
> +return;
Hm, the tabs were there but they got eaten when I replied.
Your mail seems to be base64-encoded which I don't think is
acceptable for patches -- they should be posted as plain text.
[...]
MBR, Sergey
prev parent reply other threads:[~2022-04-01 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:04 [PATCH v1] MIPS: ip22-gio: Add check for the return value of kzalloc() QintaoShen
2022-03-29 8:35 ` Sergey Shtylyov
[not found] ` <16aa9238.4bf6.17fd8fe37ad.Coremail.unsimple1993@163.com>
2022-04-01 9:09 ` Sergey Shtylyov [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=4eb43887-44a4-4693-8488-4847d80b6bd8@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
--cc=unsimple1993@163.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