All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: wg@grandegger.com, nicolas.ferre@microchip.com,
	alexandre.belloni@bootlin.com, claudiu.beznea@microchip.com,
	appana.durga.rao@xilinx.com, naga.sureshkumar.relli@xilinx.com,
	michal.simek@xilinx.com, dariobin@libero.it,
	stefan.maetje@esd.eu, mailhol.vincent@wanadoo.fr,
	yoshihiro.shimoda.uh@renesas.com,
	prabhakar.mahadev-lad.rj@bp.renesas.com, uli+renesas@fpond.eu,
	linux-can@vger.kernel.org
Subject: Re: [PATCH can-next] can: move to netif_napi_add_weight()
Date: Tue, 17 May 2022 08:10:51 +0200	[thread overview]
Message-ID: <20220517061051.kukqzmfvtiyhu37g@pengutronix.de> (raw)
In-Reply-To: <20220517002345.1812104-1-kuba@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

On 16.05.2022 17:23:45, Jakub Kicinski wrote:
> We want to remove the weight argument from the basic version of
> the netif_napi_add() call. Move all the callers in drivers/net/can
> that pass a custom weight (i.e. not NAPI_POLL_WEIGHT or 64) to
> the netif_napi_add_weight() API.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Applied to linux-can-next/testing.

Tnx,
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 --]

      reply	other threads:[~2022-05-17  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  0:23 [PATCH can-next] can: move to netif_napi_add_weight() Jakub Kicinski
2022-05-17  6:10 ` 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=20220517061051.kukqzmfvtiyhu37g@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=alexandre.belloni@bootlin.com \
    --cc=appana.durga.rao@xilinx.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=dariobin@libero.it \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=michal.simek@xilinx.com \
    --cc=naga.sureshkumar.relli@xilinx.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=stefan.maetje@esd.eu \
    --cc=uli+renesas@fpond.eu \
    --cc=wg@grandegger.com \
    --cc=yoshihiro.shimoda.uh@renesas.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 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.