From: Diksha Kumari <dikshakdevgan@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Diksha Kumari <dkdevgan@outlook.com>,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robert Moore <robert.moore@intel.com>
Subject: Re: [PATCH V2] acpi: remove unnecessary parenthesis from return statement
Date: Sun, 3 Aug 2025 22:24:34 +0530 [thread overview]
Message-ID: <b30ef694-56c2-4023-8d6e-de8f7b8e10e6@gmail.com> (raw)
In-Reply-To: <a62ff710-4216-4c4a-9ca1-b376a3703531@web.de>
On 03/08/25 21:38, Markus Elfring wrote:
>> checkpatch.pl is generating a warning when return value is enclosed
>> in parenthesis. Remove the parenthesis to improve code readability.
> parentheses?
This is my first patch, so i am not sure what you mean by this.
>
> You propose to omit also some curly brackets, don't you?
ok, i will include this in the next version.
>
> …> ---
>> drivers/acpi/acpica/dbconvert.c | 43 +++++++++++++++------------------
> …
>
> Did you overlook the addition of patch version descriptions?
> https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n310
yes, went through the document, thanks for the information. I will add
the change log in next version.
Thanks for reviewing the patch and feedback.
Regards,
Diksha
> Regards,
> Markus
next prev parent reply other threads:[~2025-08-03 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 15:38 [PATCH V2] acpi: remove unnecessary parenthesis from return statement Diksha Kumari
2025-08-03 16:08 ` Markus Elfring
2025-08-03 16:54 ` Diksha Kumari [this message]
2025-08-12 13:07 ` Rafael J. Wysocki
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=b30ef694-56c2-4023-8d6e-de8f7b8e10e6@gmail.com \
--to=dikshakdevgan@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=acpica-devel@lists.linux.dev \
--cc=dkdevgan@outlook.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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 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.