From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Romain Naour <romain.naour@smile.fr>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Nishanth Menon <nm@ti.com>,
linux-mmc@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: sdhci-omap: issues with PM features since 5.16
Date: Tue, 13 Feb 2024 14:58:01 +0200 [thread overview]
Message-ID: <20240213125801.GH52537@atomide.com> (raw)
In-Reply-To: <CAHCN7x+Uswxzj3eTf1_9oqso0fpdVR5QHNQkd59zHSqx5CyeCw@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [240213 12:43]:
> On Tue, Feb 13, 2024 at 12:03 AM Tony Lindgren <tony@atomide.com> wrote:
> > Assuming no issues and if the hs200 issue is a separate issue, maybe
> > post the patches and then let's get some Tested-by for them before we
> > put them into Linux next.
>
> I just sent a patch against omap3.dtsi.
> I am not sure how to handle the backwards compatible device tree breakage.
Thanks, I replied to the patch on the properties for sdhci.
Regards,
Tony
next prev parent reply other threads:[~2024-02-13 12:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 20:53 sdhci-omap: issues with PM features since 5.16 Romain Naour
2024-01-27 4:48 ` Tony Lindgren
2024-01-29 10:11 ` Romain Naour
2024-01-29 11:17 ` Tony Lindgren
2024-01-29 17:42 ` Romain Naour
2024-01-30 11:14 ` Romain Naour
2024-01-31 10:30 ` Tony Lindgren
2024-02-01 9:04 ` Romain Naour
2024-02-02 4:36 ` Tony Lindgren
2024-02-08 11:29 ` Romain Naour
2024-02-08 12:57 ` Adam Ford
2024-02-12 7:27 ` Tony Lindgren
2024-02-12 13:24 ` Adam Ford
2024-02-13 6:03 ` Tony Lindgren
2024-02-13 12:43 ` Adam Ford
2024-02-13 12:58 ` Tony Lindgren [this message]
2024-03-15 23:49 ` Romain Naour
2024-03-21 9:48 ` Tony Lindgren
2024-01-30 11:15 ` Tony Lindgren
2024-01-30 11:22 ` Romain Naour
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=20240213125801.GH52537@atomide.com \
--to=tony@atomide.com \
--cc=adrian.hunter@intel.com \
--cc=aford173@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=romain.naour@smile.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox