[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbe0314d-bfd3-cb0c-8af8-ab5bab276cc3@xilinx.com>
Date: Wed, 9 Feb 2022 09:41:47 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Srinivas Neeli <sneeli@...inx.com>,
Marc Kleine-Budde <mkl@...gutronix.de>
CC: "wg@...ndegger.com" <wg@...ndegger.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Appana Durga Kedareswara Rao <appanad@...inx.com>,
Srinivas Goud <sgoud@...inx.com>, git <git@...inx.com>
Subject: Re: [PATCH] can: xilinx_can: Add check for NAPI Poll function
Hi,
On 2/9/22 09:40, Srinivas Neeli wrote:
> Hi Marc,
>
>> -----Original Message-----
>> From: Marc Kleine-Budde <mkl@...gutronix.de>
>> Sent: Wednesday, February 9, 2022 2:02 PM
>> To: Srinivas Neeli <sneeli@...inx.com>
>> Cc: wg@...ndegger.com; davem@...emloft.net; kuba@...nel.org; Michal
>> Simek <michals@...inx.com>; linux-can@...r.kernel.org;
>> netdev@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
>> kernel@...r.kernel.org; Appana Durga Kedareswara Rao
>> <appanad@...inx.com>; Srinivas Goud <sgoud@...inx.com>; git
>> <git@...inx.com>
>> Subject: Re: [PATCH] can: xilinx_can: Add check for NAPI Poll function
>>
>> On 09.02.2022 08:29:55, Srinivas Neeli wrote:
>>>> On 08.02.2022 21:50:53, Srinivas Neeli wrote:
>>>>> Add check for NAPI poll function to avoid enabling interrupts with
>>>>> out completing the NAPI call.
>>>>
>>>> Thanks for the patch. Does this fix a bug? If so, please add a Fixes:
>>>> tag that lists the patch that introduced that bug.
>>>
>>> It is not a bug. I am adding additional safety check( Validating the
>>> return value of "napi_complete_done" call).
>>
>> Thanks for your feedback. Should this go into can or can-next?
>
> If possible please apply on both branches.
New feature should come to next. It means can-next please.
Thanks,
Michal
Powered by blists - more mailing lists