From: "Zhang, Rui" <rui.zhang@intel.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
"peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vkuznets@redhat.com" <vkuznets@redhat.com>
Subject: Re: [PATCH] cpu/SMT: Fix cpu_smt_possible() comment
Date: Fri, 28 Jul 2023 15:57:22 +0000 [thread overview]
Message-ID: <5fd67ff4c295ae01be79b5a0101c17bc5f5ef5bd.camel@intel.com> (raw)
In-Reply-To: <87zg3gqykl.ffs@tglx>
Hi, Thomas,
On Fri, 2023-07-28 at 09:34 +0200, Thomas Gleixner wrote:
> On Mon, Jul 10 2023 at 11:21, Zhang Rui wrote:
> > The comment of cpu_smt_possible() is not aligned with the changelog
> > of
> > commit e1572f1d08be ("cpu/SMT: create and export
> > cpu_smt_possible()"),
> > and it is wrong.
>
> Why? Do I need to go and read that commit log and figure out what's
> wrong?
>
> > Fix cpu_smt_possible() comment.
>
> Zero information.
>
Thanks for reviewing. Sent patch V2 with changelog rephrased.
thanks,
rui
prev parent reply other threads:[~2023-07-28 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 3:21 Zhang Rui
2023-07-10 7:36 ` Vitaly Kuznetsov
2023-07-28 7:34 ` Thomas Gleixner
2023-07-28 15:57 ` Zhang, Rui [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=5fd67ff4c295ae01be79b5a0101c17bc5f5ef5bd.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.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
Powered by JetHome