From: "Luck, Tony" <tony.luck@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: RE: [PATCH] topology: Fix up build warning in topology_is_visible()
Date: Sun, 24 Apr 2022 18:08:09 +0000 [thread overview]
Message-ID: <bbe4472b8ba54b259f011c6ed9808d6a@intel.com> (raw)
In-Reply-To: <YmPajtfsCL8Idw4h@kroah.com>
> Given no comments that this is a bad idea, I'll go apply this now.
FWIW (very little) 0-day didn't find issues with changing from macro to
static inline. But your fix is much neater.
-Tony
prev parent reply other threads:[~2022-04-24 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 6:26 [PATCH] topology: Fix up build warning in topology_is_visible() Greg Kroah-Hartman
2022-04-23 10:53 ` Greg Kroah-Hartman
2022-04-24 18:08 ` Luck, Tony [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=bbe4472b8ba54b259f011c6ed9808d6a@intel.com \
--to=tony.luck@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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