netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ziyang Xuan <william.xuanziyang@huawei.com>,
	mkl@pengutronix.de, davem@davemloft.net, kuba@kernel.org,
	linux-can@vger.kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] can: bcm: can: bcm: random optimizations
Date: Thu, 15 Sep 2022 07:21:25 +0200	[thread overview]
Message-ID: <2f30f0f3-aafc-6f15-b7e5-fa47595dcc63@hartkopp.net> (raw)
In-Reply-To: <cover.1663206163.git.william.xuanziyang@huawei.com>



On 15.09.22 03:55, Ziyang Xuan wrote:
> Do some small optimization for can_bcm.
> 
> ---
> v2:
>    - Continue to update currframe when can_send() failed in patch 2.
>    - Remove ‘Fixes’ tag in patch 2.

For this series:

Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>

Many Thanks!

> 
> Ziyang Xuan (2):
>    can: bcm: registration process optimization in bcm_module_init()
>    can: bcm: check the result of can_send() in bcm_can_tx()
> 
>   net/can/bcm.c | 25 +++++++++++++++++++------
>   1 file changed, 19 insertions(+), 6 deletions(-)
> 

  parent reply	other threads:[~2022-09-15  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  1:55 [PATCH v2 0/2] can: bcm: can: bcm: random optimizations Ziyang Xuan
2022-09-15  1:55 ` [PATCH v2 1/2] can: bcm: registration process optimization in bcm_module_init() Ziyang Xuan
2022-09-15  1:55 ` [PATCH v2 2/2] can: bcm: check the result of can_send() in bcm_can_tx() Ziyang Xuan
2022-09-15  5:21 ` Oliver Hartkopp [this message]
2022-09-23 12:12 ` [PATCH v2 0/2] can: bcm: can: bcm: random optimizations Marc Kleine-Budde

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=2f30f0f3-aafc-6f15-b7e5-fa47595dcc63@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=william.xuanziyang@huawei.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).