From: "Christian Löhle" <CLoehle@hyperstone.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Ricky WU <ricky_wu@realtek.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mmc: rtsx: add 74 Clocks in power on flow
Date: Mon, 9 May 2022 10:12:45 +0000 [thread overview]
Message-ID: <050affc68f7f4861b35a1ab96e228fec@hyperstone.com> (raw)
In-Reply-To: <YnjjR8pouD4KtHtT@kroah.com>
>> Can we get 1f311c94aabdb419c28e3147bcc8ab89269f1a7e merged into the stable tree?
>
>Which stable branches do you want this added to?
>
>thanks,
>
>greg k-h
From what I can tell the issue is present since the addition of the driver in ff984e57d36e8
So I would suggest adding them to all? Maybe Ricky and Ulf could comment?
Regards,
Christian=
Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
next prev parent reply other threads:[~2022-05-09 10:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 7:27 [PATCH] mmc: rtsx: add 74 Clocks in power on flow Ricky WU
2022-02-22 7:42 ` gregkh
2022-02-22 8:48 ` Ricky WU
2022-02-22 8:59 ` gregkh
2022-02-22 12:31 ` Ricky WU
2022-02-22 14:18 ` gregkh
2022-02-24 5:49 ` Ricky WU
2022-02-28 16:12 ` Ulf Hansson
2022-05-09 9:35 ` Christian Löhle
2022-05-09 9:47 ` gregkh
2022-05-09 10:12 ` Christian Löhle [this message]
2022-05-10 9:56 ` Ulf Hansson
2022-05-10 10:21 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2022-05-10 12:08 Christian Löhle
2022-05-10 12:09 ` Christian Löhle
2022-05-10 12:40 ` Greg Kroah-Hartman
2022-05-10 13:00 Christian Löhle
2022-05-10 13:02 ` Christian Löhle
2022-05-13 7:54 ` Greg Kroah-Hartman
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=050affc68f7f4861b35a1ab96e228fec@hyperstone.com \
--to=cloehle@hyperstone.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.