Linux-USB Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hayes Wang <hayeswang@realtek.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	nic_swsd@realtek.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next] r8152: replace dev_info with dev_dbg for loading firmware
Date: Fri, 26 Apr 2024 02:10:26 +0000	[thread overview]
Message-ID: <171409742644.3002.17427557542313626166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240424084532.159649-1-hayeswang@realtek.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 24 Apr 2024 16:45:32 +0800 you wrote:
> Someone complains the message appears continuously. This occurs
> because the device is woken from UPS mode, and the driver re-loads
> the firmware.
> 
> When the device enters runtime suspend and cable is unplugged, the
> device would enter UPS mode. If the runtime resume occurs, and the
> device is woken from UPS mode, the driver has to re-load the firmware
> and causes the message. If someone wakes the device continuously, the
> message would be shown continuously, too. Use dev_dbg to avoid it.
> 
> [...]

Here is the summary with links:
  - [net-next] r8152: replace dev_info with dev_dbg for loading firmware
    https://git.kernel.org/netdev/net-next/c/092d214138fd

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



      parent reply	other threads:[~2024-04-26  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  8:45 [PATCH net-next] r8152: replace dev_info with dev_dbg for loading firmware Hayes Wang
2024-04-24  9:04 ` Hariprasad Kelam
2024-04-26  2:10 ` 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=171409742644.3002.17427557542313626166.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hayeswang@realtek.com \
    --cc=kuba@kernel.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).