[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <021d01d5ac01$d55f1220$801d3660$@samsung.com>
Date: Fri, 6 Dec 2019 12:23:11 +0530
From: "pankj.sharma" <pankj.sharma@...sung.com>
To: "'Dan Murphy'" <dmurphy@...com>
Cc: <wg@...ndegger.com>, <mkl@...gutronix.de>, <davem@...emloft.net>,
<rcsekar@...sung.com>, <pankaj.dubey@...sung.com>,
<linux-can@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/2] can: m_can_platform: Bug fix of kernel panic for
> From: Dan Murphy <dmurphy@...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.
Hello Dan,
I haven’t copied to linux-stable, but the patches are already in linux-stable branch.
You can check in following link.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.4.y
Pankaj
>
> Or at the very least see if the stable automation will pick these up.
>
> Dan
>
Powered by blists - more mailing lists