linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hayes Wang <hayeswang@realtek.com>
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] r8152: adjust flow for power cut
Date: Fri, 05 Feb 2021 05:00:07 +0000	[thread overview]
Message-ID: <161250120781.4551.10548606123432458434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1394712342-15778-398-Taiwan-albertk@realtek.com>

Hello:

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

On Wed, 3 Feb 2021 17:14:27 +0800 you wrote:
> The two patches are used to adjust the flow about resuming from
> the state of power cut. For the purpose, some functions have to
> be updated first.
> 
> Hayes Wang (2):
>   r8152: replace several functions about phy patch request
>   r8152: adjust the flow of power cut for RTL8153B
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] r8152: replace several functions about phy patch request
    https://git.kernel.org/netdev/net-next/c/a08c0d309d8c
  - [net-next,2/2] r8152: adjust the flow of power cut for RTL8153B
    https://git.kernel.org/netdev/net-next/c/80fd850b31f0

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-02-05  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  9:14 [PATCH net-next 0/2] r8152: adjust flow for power cut Hayes Wang
2021-02-03  9:14 ` [PATCH net-next 1/2] r8152: replace several functions about phy patch request Hayes Wang
2021-02-03  9:14 ` [PATCH net-next 2/2] r8152: adjust the flow of power cut for RTL8153B Hayes Wang
2021-02-05  5:00 ` patchwork-bot+netdevbpf [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=161250120781.4551.10548606123432458434.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=hayeswang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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).