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:38:52 -0700 [thread overview]
Message-ID: <20190723063852.GO5447@atomide.com> (raw)
In-Reply-To: <d66357e0-62e1-6132-00a1-a9c48ca3e481@lechnology.com>
Hi,
* David Lechner <david@lechnology.com> [190722 14:55]:
> Not sure if this is related, but this is what I get on v5.3-rc1
> with this patch (wifi still not working, obviously):
>
> [ 21.952767] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [ 22.011340] ------------[ cut here ]------------
> [ 22.016402] WARNING: CPU: 0 PID: 65 at /home/david/work/ev3dev2/ev3dev-kernel/net/wireless/core.c:868 wiphy_register+0x860/0xba0 [cfg80211]
This one is fixed in Linux next but missed -rc1, see thread
"nl80211 wlcore regression in next".
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
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:38:52 -0700 [thread overview]
Message-ID: <20190723063852.GO5447@atomide.com> (raw)
In-Reply-To: <d66357e0-62e1-6132-00a1-a9c48ca3e481@lechnology.com>
Hi,
* David Lechner <david@lechnology.com> [190722 14:55]:
> Not sure if this is related, but this is what I get on v5.3-rc1
> with this patch (wifi still not working, obviously):
>
> [ 21.952767] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [ 22.011340] ------------[ cut here ]------------
> [ 22.016402] WARNING: CPU: 0 PID: 65 at /home/david/work/ev3dev2/ev3dev-kernel/net/wireless/core.c:868 wiphy_register+0x860/0xba0 [cfg80211]
This one is fixed in Linux next but missed -rc1, see thread
"nl80211 wlcore regression in next".
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:38 UTC|newest]
Thread overview: 24+ 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 ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 1/4] ARM: OMAP2+: Drop mmc platform data for am330x and am43xx Tony Lindgren
2019-03-26 18:13 ` Tony Lindgren
2019-07-21 2:42 ` David Lechner
2019-07-21 2:42 ` David Lechner
2019-07-22 6:09 ` Tony Lindgren
2019-07-22 6:09 ` Tony Lindgren
2019-07-22 7:54 ` Tony Lindgren
2019-07-22 7:54 ` Tony Lindgren
2019-07-22 14:27 ` David Lechner
2019-07-22 14:27 ` David Lechner
2019-07-23 6:40 ` Tony Lindgren
2019-07-23 6:40 ` Tony Lindgren
2019-07-22 14:54 ` David Lechner
2019-07-22 14:54 ` David Lechner
2019-07-23 6:38 ` Tony Lindgren [this message]
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 ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 3/4] ARM: OMAP2+: Drop gpio " Tony Lindgren
2019-03-26 18:13 ` Tony Lindgren
2019-03-26 18:13 ` [PATCH 4/4] ARM: OMAP2+: Drop uart " Tony Lindgren
2019-03-26 18:13 ` 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=20190723063852.GO5447@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 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.