From: Tony Lindgren <tony@atomide.com>
To: David Lechner <david@lechnology.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx
Date: Mon, 22 Jul 2019 23:40:38 -0700 [thread overview]
Message-ID: <20190723064038.GP5447@atomide.com> (raw)
In-Reply-To: <8427af44-2e28-7e13-3841-15c89d60f6dd@lechnology.com>
* David Lechner <david@lechnology.com> [190722 14:27]:
> On 7/22/19 2:54 AM, Tony Lindgren wrote:
> > Oh I just noticed this needs to be fixed in v5.2, not in v5.3-rc
> > series. It's best to keep the "ti,hwmods" property still around
> > as there may be dependencies to ti-sysc driver changes in v5.3-rc
> > series for dropping it. Below is a more minimal fix to try.
...
> This fixes wifi on BeagleBone Blue for me in v5.2.
>
> Tested-by: David Lechner <david@lechnology.com>
OK great, thanks for testing.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-23 6:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 18:13 [PATCH 0/4] drop selected platform data for am3 and am4 Tony Lindgren
2019-03-26 18:13 ` [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx Tony Lindgren
2019-07-21 2:42 ` David Lechner
2019-07-22 6:09 ` Tony Lindgren
2019-07-22 7:54 ` Tony Lindgren
2019-07-22 14:27 ` David Lechner
2019-07-23 6:40 ` Tony Lindgren [this message]
2019-07-22 14:54 ` David Lechner
2019-07-23 6:38 ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 2/4] ARM: OMAP2+: Drop i2c platform data for am33xx " Tony Lindgren
2019-03-26 18:13 ` [PATCH 3/4] ARM: OMAP2+: Drop gpio " Tony Lindgren
2019-03-26 18:13 ` [PATCH 4/4] ARM: OMAP2+: Drop uart " Tony Lindgren
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=20190723064038.GP5447@atomide.com \
--to=tony@atomide.com \
--cc=david@lechnology.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).