[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0550b0b-6681-75a3-c58a-28f5b7ca0821@ti.com>
Date: Thu, 5 Dec 2019 14:57:26 -0600
From: Dan Murphy <dmurphy@...com>
To: Pankaj Sharma <pankj.sharma@...sung.com>,
<linux-can@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
CC: <wg@...ndegger.com>, <mkl@...gutronix.de>, <davem@...emloft.net>,
<rcsekar@...sung.com>, <pankaj.dubey@...sung.com>
Subject: Re: [PATCH 0/2] can: m_can_platform: Bug fix of kernel panic for
Pankaj
On 11/19/19 4:20 AM, Pankaj Sharma wrote:
> The current code is failing while clock prepare enable because of not
> getting proper clock from platform device.
> A device driver for CAN controller hardware registers itself with the
> Linux network layer as a network device. So, the driver data for m_can
> should ideally be of type net_device.
>
> Further even when passing the proper net device in probe function the
> code was hanging because of the function m_can_runtime_resume() getting
> recursively called from m_can_class_resume().
>
> Pankaj Sharma (2):
> can: m_can_platform: set net_device structure as driver data
> can: m_can_platform: remove unnecessary m_can_class_resume() call
Did you CC: linux-stable for these? We are probably going to have
customers picking up 5.4 LTS and would need these bug fixes.
Or at the very least see if the stable automation will pick these up.
Dan
Powered by blists - more mailing lists