From: Adrian Hunter <adrian.hunter@intel.com>
To: Sven van Ashbrook <svenva@chromium.org>,
ulf.hansson@linaro.org, ben.chuang@genesyslogic.com.tw,
jasonlai.genesyslogic@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
jason.lai@genesyslogic.com.tw, skardach@google.com,
Renius Chen <reniuschengl@gmail.com>,
rafael.j.wysocki@intel.com, linux-mmc@vger.kernel.org,
stable@vger.kernel.org, SeanHY.chen@genesyslogic.com.tw,
victor.shih@genesyslogic.com.tw, greg.tu@genesyslogic.com.tw
Subject: Re: [PATCH v3] mmc: sdhci-pci-gli: fix LPM negotiation so x86/S0ix SoCs can suspend
Date: Wed, 6 Sep 2023 08:33:39 +0300 [thread overview]
Message-ID: <7035c4ba-2432-2bde-27dc-601b4df74ea7@intel.com> (raw)
In-Reply-To: <CAG-rBig796Yc9iyTiLOLt2R9PW9SoOFtuks3a1usu4XwvkzAOQ@mail.gmail.com>
On 5/09/23 21:15, Sven van Ashbrook wrote:
> What do we need for Ulf to add this to the maintainer git?
Nothing, it will get processed in due course, likely making it into
one of the 6.6 release candidates, because it is a fix, and from
there to stable.
But right now is the middle of the merge window so some delay can
be expected anyway.
> What do we need for Ulf to add this to the maintainer git? There are
> There are
> released devices waiting for this fix, but picking from list generates
> lots of paperwork, so I'd prefer to pick from git.
>
> We have a LGTM from Jason Lai, do we need one from Ben Chuang as well?
>
> On Mon, Sep 4, 2023 at 3:42 AM Adrian Hunter <adrian.hunter@intel.com> wrote:
>>
>> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
>>
next prev parent reply other threads:[~2023-09-06 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 16:00 [PATCH v3] mmc: sdhci-pci-gli: fix LPM negotiation so x86/S0ix SoCs can suspend Sven van Ashbrook
2023-09-01 6:33 ` Lai Jason
2023-09-01 12:40 ` Adrian Hunter
2023-09-04 10:39 ` Adrian Hunter
2023-09-05 18:15 ` Sven van Ashbrook
2023-09-06 2:25 ` Ben Chuang
2023-09-06 5:33 ` Adrian Hunter [this message]
2023-09-14 13:02 ` Ulf Hansson
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=7035c4ba-2432-2bde-27dc-601b4df74ea7@intel.com \
--to=adrian.hunter@intel.com \
--cc=SeanHY.chen@genesyslogic.com.tw \
--cc=ben.chuang@genesyslogic.com.tw \
--cc=greg.tu@genesyslogic.com.tw \
--cc=jason.lai@genesyslogic.com.tw \
--cc=jasonlai.genesyslogic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=reniuschengl@gmail.com \
--cc=skardach@google.com \
--cc=stable@vger.kernel.org \
--cc=svenva@chromium.org \
--cc=ulf.hansson@linaro.org \
--cc=victor.shih@genesyslogic.com.tw \
/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