mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	andrew@lunn.ch, vivien.didelot@gmail.com, davem@davemloft.net,
	kuba@kernel.org
Subject: Re: [PATCH -next 0/2] net: dsa: qca8k: check return value of read functions correctly
Date: Sun, 30 May 2021 21:30:03 +0000	[thread overview]
Message-ID: <162241020389.28062.11780687438412526586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210529030439.1723306-1-yangyingliang@huawei.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Sat, 29 May 2021 11:04:37 +0800 you wrote:
> patch #1 - Change return type and add output parameter to make check
> return value of read  functions correctly.
> 
> patch #2 - Add missing check return value in qca8k_phylink_mac_config().
> 
> v2:
>   move 'int ret' to patch #2.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net: dsa: qca8k: check return value of read functions correctly
    https://git.kernel.org/netdev/net-next/c/7c9896e37807
  - [net-next,v2,2/2] net: dsa: qca8k: add missing check return value in qca8k_phylink_mac_config()
    https://git.kernel.org/netdev/net-next/c/9fe99de01440

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2021-05-30 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29  3:04 Yang Yingliang
2021-05-29  3:04 ` [PATCH net-next v2 1/2] " Yang Yingliang
2021-05-29  3:04 ` [PATCH net-next v2 2/2] net: dsa: qca8k: add missing check return value in qca8k_phylink_mac_config() Yang Yingliang
2021-05-30 21:30 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-28  8:22 [PATCH -next 0/2] net: dsa: qca8k: check return value of read functions correctly Yang Yingliang

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=162241020389.28062.11780687438412526586.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=yangyingliang@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

all inboxes | Powered by JetHome®