From: Bjorn Helgaas <helgaas@kernel.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: lkp <lkp@intel.com>, "rafael@kernel.org" <rafael@kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"Jonathan.Cameron@Huawei.com" <Jonathan.Cameron@Huawei.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Moore, Robert" <robert.moore@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"dave@stgolabs.net" <dave@stgolabs.net>
Subject: Re: [PATCH v3 3/3] acpi/pci_root: negotiate CXL _OSC
Date: Wed, 30 Mar 2022 15:30:42 -0500 [thread overview]
Message-ID: <20220330203042.GA1707046@bhelgaas> (raw)
In-Reply-To: <4a6543cf79e66ecd5ec5c15da5bec74d3602cb07.camel@intel.com>
On Wed, Mar 30, 2022 at 08:16:29PM +0000, Verma, Vishal L wrote:
> On Wed, 2022-03-30 at 14:01 -0500, Bjorn Helgaas wrote:
> > > Reported-by: kernel test robot <lkp@intel.com>
> >
> > What was reported by the robot? If it just complained about something
> > in v1 or v2, I think there's no point in mentioning this here. It's
> > the same as ordinary review comments (like these I'm composing), and
> > they don't need to be acknowledged. I think "Reported-by" is great
> > when giving credit for bug fixes, but that's not what's happening
> > here.
>
> Correct it was a compile warning, and actually it wasn't on-list - 0day
> sent it privately, because it was on the RFC version. It makes sense to
> treat it as a normal review comment - I only added the tag because the
> 0day emails ask you to (I suppose they use the trailers for metrics on
> actionable feedback generated by the bot). I'm happy to drop it if
> that's preferred here.
Yeah, I know. I *love* the 0-day bot and the fact that it tests
things before they're even merged, but I wish it would only ask you to
add the tag if it's something that has already been merged, where the
likely outcome is a tiny bug-fix patch where it's obvious what
"Reported-by" refers to.
Bjorn
prev parent reply other threads:[~2022-03-30 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 18:14 [PATCH v3 0/3] acpi: add support for CXL _OSC Vishal Verma
2022-03-30 18:14 ` [PATCH v3 1/3] acpi: add a helper for retrieving _OSC Control DWORDs Vishal Verma
2022-03-30 19:04 ` Bjorn Helgaas
2022-03-30 20:08 ` Verma, Vishal L
2022-03-30 18:14 ` [PATCH v3 2/3] PCI/ACPI: Use CXL _OSC instead of PCIe _OSC Vishal Verma
2022-03-30 18:14 ` [PATCH v3 3/3] acpi/pci_root: negotiate CXL _OSC Vishal Verma
2022-03-30 19:01 ` Bjorn Helgaas
2022-03-30 20:16 ` Verma, Vishal L
2022-03-30 20:30 ` Bjorn Helgaas [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=20220330203042.GA1707046@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=vishal.l.verma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox