From: Yuma Ueda <cyan@0x00a1e9.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-kernel@vger.kernel.org, keescook@chromium.org,
gregkh@linuxfoundation.org, ojeda@kernel.org,
boqun.feng@gmail.com, masahiroy@kernel.org,
samitolvanen@google.com, ytcoode@gmail.com
Subject: Re: [PATCH v2] scripts/kallsyms.c Make the comment up-to-date with current implementation
Date: Fri, 18 Nov 2022 22:27:11 +0900 [thread overview]
Message-ID: <20221118132704.GA2288@0x00a1e9.dev> (raw)
In-Reply-To: <CANiq72nJ8OutiA48zzXkZUvfGFjEWazPOgzXtqV2-J5HnDWx=w@mail.gmail.com>
Thank you for your comment.
On Wed, Nov 16, 2022 at 09:04:22PM +0100, Miguel Ojeda wrote:
> On Tue, Nov 15, 2022 at 10:26 PM Yuma Ueda <cyan@0x00a1e9.dev> wrote:
> >
> > The comment in scripts/kallsyms.c describing the usage of
> > scripts/kallsyms does not reflect the latest implementation.
> > Fix the comment to be up-to-date with the current implementation.
>
> It may be a good idea to say in the commit message that this is now
> equivalent to what the `usage()` function prints (and possibly change
> `scripts/kallsyms` to just `kallsyms` to make it exactly equal).
I'll change it that way for both.
> In fact, we could replace the comment with "See usage() function" to
> avoid further desyncs... But that is a different patch :)
>
I don't know if the comment should just be changed to "See usage() function",
and as you said, that should be done in a different patch,
so for now I will send a patch that fixes the issues you mentioned.
> Also, I am not sure we want to use tabs on the comment -- the rest of
> it uses spaces.
OK, I'll change tabs into spaces.
>
> Cheers,
> Miguel
I'll send a new version of the patch later.
Regards,
Yuma Ueda
prev parent reply other threads:[~2022-11-18 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 21:25 [PATCH v2] scripts/kallsyms.c Make the comment up-to-date with current implementation Yuma Ueda
2022-11-16 20:04 ` Miguel Ojeda
2022-11-18 13:27 ` Yuma Ueda [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=20221118132704.GA2288@0x00a1e9.dev \
--to=cyan@0x00a1e9.dev \
--cc=boqun.feng@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=samitolvanen@google.com \
--cc=ytcoode@gmail.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