From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Charalampos Mitrodimas <charmitro@posteo.net>,
Sebastian Reichel <sre@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mario Limonciello <mario.limonciello@amd.com>,
qinyu <qinyu32@huawei.com>, Nick Alcock <nick.alcock@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Huacai Chen <chenhuacai@kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Andreas Kemnade <andreas@kemnade.info>,
Ian Molton <spyro@f2s.com>,
Szabolcs Gyurko <szabolcs.gyurko@tlt.hu>,
Anton Vorontsov <cbou@mail.ru>
Cc: Linux Power Management <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] power: supply: Fix indentation and some other warnings
Date: Sat, 18 Nov 2023 18:45:49 +0700 [thread overview]
Message-ID: <06648cde-e8d9-42d0-a8ef-15c9a9b8850a@gmail.com> (raw)
In-Reply-To: <CX1VDFVCGNKO.3JX5QY0LZQ51B@beast>
On 11/18/23 17:36, Charalampos Mitrodimas wrote:
> Hi Bagas,
>
> On Sat Nov 18, 2023 at 1:36 AM EET, Bagas Sanjaya wrote:
>> On Fri, Nov 17, 2023 at 11:06:58PM +0000, Charalampos Mitrodimas wrote:
>>> These were mentioned by checkpatch:
>>> Errors:
>>> (1) code indent should use tabs where possible
>>> (2) switch and case should be at the same indent
>>> Warnings:
>>> (1) quoted string split across lines
>>> (2) Missing a blank line after declarations
>>>
>>> Based on this comment from "include/linux/module.h", modules with
>>> multiple authors should use multiple MODULE_AUTHOR() statements.
>>> /*
>>> * Author(s), use "Name <email>" or just "Name", for multiple
>>> * authors use multiple MODULE_AUTHOR() statements/lines.
>>> */
>>> #define MODULE_AUTHOR(_author) MODULE_INFO(author, _author)
>>
>> Shouldn't MODULE_AUTHOR fix be separate patch?
>
> Sorry, I should have mentioned in the commit that the warnings "quoted
> string split across lines" pertained to the MODULE_AUTHOR line.
>
> In the commit message I'm just clarifying why I used multiple
> MODULE_AUTHOR statements.
>
> Should I send a v2 patch with a revised commit description?
>
OK but as separate patch.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-11-18 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 23:06 [PATCH] power: supply: Fix indentation and some other warnings Charalampos Mitrodimas
2023-11-17 23:36 ` Bagas Sanjaya
2023-11-18 10:36 ` Charalampos Mitrodimas
2023-11-18 11:45 ` Bagas Sanjaya [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=06648cde-e8d9-42d0-a8ef-15c9a9b8850a@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andreas@kemnade.info \
--cc=cbou@mail.ru \
--cc=charmitro@posteo.net \
--cc=chenhuacai@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nick.alcock@oracle.com \
--cc=qinyu32@huawei.com \
--cc=rafael.j.wysocki@intel.com \
--cc=spyro@f2s.com \
--cc=sre@kernel.org \
--cc=szabolcs.gyurko@tlt.hu \
/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