From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Srinivas Neeli <sneeli@xilinx.com>
Cc: "wg@grandegger.com" <wg@grandegger.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
Michal Simek <michals@xilinx.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Appana Durga Kedareswara Rao <appanad@xilinx.com>,
Srinivas Goud <sgoud@xilinx.com>, git <git@xilinx.com>
Subject: Re: [PATCH] can: xilinx_can: Add check for NAPI Poll function
Date: Wed, 9 Feb 2022 09:43:55 +0100 [thread overview]
Message-ID: <20220209084355.2q5xjrodusfsudtb@pengutronix.de> (raw)
In-Reply-To: <DM6PR02MB53867DD5740FAA93CB5BC3B4AF2E9@DM6PR02MB5386.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
On 09.02.2022 08:40:48, Srinivas Neeli wrote:
> Hi Marc,
>
> > -----Original Message-----
> > From: Marc Kleine-Budde <mkl@pengutronix.de>
> > Sent: Wednesday, February 9, 2022 2:02 PM
> > To: Srinivas Neeli <sneeli@xilinx.com>
> > Cc: wg@grandegger.com; davem@davemloft.net; kuba@kernel.org; Michal
> > Simek <michals@xilinx.com>; linux-can@vger.kernel.org;
> > netdev@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> > kernel@vger.kernel.org; Appana Durga Kedareswara Rao
> > <appanad@xilinx.com>; Srinivas Goud <sgoud@xilinx.com>; git
> > <git@xilinx.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.
That's not an option. Going for can-next as Michal Simek suggested.
Adding to linux-can-next/testing.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-02-09 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:20 [PATCH] can: xilinx_can: Add check for NAPI Poll function Srinivas Neeli
2022-02-09 7:49 ` Marc Kleine-Budde
2022-02-09 8:29 ` Srinivas Neeli
2022-02-09 8:31 ` Marc Kleine-Budde
2022-02-09 8:40 ` Srinivas Neeli
2022-02-09 8:41 ` Michal Simek
2022-02-09 8:43 ` Marc Kleine-Budde [this message]
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=20220209084355.2q5xjrodusfsudtb@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=appanad@xilinx.com \
--cc=davem@davemloft.net \
--cc=git@xilinx.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=sgoud@xilinx.com \
--cc=sneeli@xilinx.com \
--cc=wg@grandegger.com \
/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).