[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4ac4ee07-9328-415f-a4e8-30dfd9c10fee@amd.com>
Date: Thu, 17 Aug 2023 13:31:35 -0500
From: "Limonciello, Mario" <mario.limonciello@....com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Bjorn Helgaas <helgaas@...nel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-acpi@...r.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Iain Lane <iain@...ngesquash.org.uk>,
Shyam-sundar S-k <Shyam-sundar.S-k@....com>
Subject: Re: [PATCH v11 9/9] PCI: ACPI: Use device constraints to decide PCI
target state fallback policy
>> I was intentionally trying to leave the actual problem out of the commit
>> from your earlier feedback and just put it in the cover letter.
>>
>> But if it's better to keep in the commit message I'll return those details.
>
> It is.
>
> If you make a change in order to address a specific problem, that
> problem needs to be described in the changelog of the patch making
> that change.
>
> Anything else is more or less confusing IMO.
Thanks. I'll write up a new commit message for v13 once I have some
feedback on the approach of 'v11' vs the 'approach of 'v12'.
Powered by blists - more mailing lists