From: Markus Elfring <Markus.Elfring@web.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
Henrik Rydberg <rydberg@bitmath.org>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [cocci] Input: MT - Return directly after a failed kzalloc() in input_mt_init_slots()
Date: Fri, 29 Dec 2023 10:00:28 +0100 [thread overview]
Message-ID: <df72e6dc-5d4a-4101-9366-24a9166ec9ba@web.de> (raw)
In-Reply-To: <ZY54hX3VLswwKgMH@google.com>
>> Thus return directly after a call of the function “kzalloc” failed
>> at the beginning.
>
> This is not needed. The same arguments as on the patch to
> usbtouchscreen.c.
I suggest to avoid redundant data processing a bit more.
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
Henrik Rydberg <rydberg@bitmath.org>,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: Input: MT - Return directly after a failed kzalloc() in input_mt_init_slots()
Date: Fri, 29 Dec 2023 10:00:28 +0100 [thread overview]
Message-ID: <df72e6dc-5d4a-4101-9366-24a9166ec9ba@web.de> (raw)
In-Reply-To: <ZY54hX3VLswwKgMH@google.com>
>> Thus return directly after a call of the function “kzalloc” failed
>> at the beginning.
>
> This is not needed. The same arguments as on the patch to
> usbtouchscreen.c.
I suggest to avoid redundant data processing a bit more.
Regards,
Markus
next prev parent reply other threads:[~2023-12-29 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 19:43 [cocci] [PATCH] Input: MT - Return directly after a failed kzalloc() in input_mt_init_slots() Markus Elfring
2023-12-26 19:43 ` Markus Elfring
2023-12-29 7:43 ` Dmitry Torokhov
2023-12-29 9:00 ` Markus Elfring [this message]
2023-12-29 9:00 ` Markus Elfring
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=df72e6dc-5d4a-4101-9366-24a9166ec9ba@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@bitmath.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.