Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, tho.vu.wh@renesas.com
Subject: Re: [PATCH net] net: ethernet: renesas: ravb: Fix promiscuous mode after system resumed
Date: Tue, 29 Nov 2022 17:00:18 +0000	[thread overview]
Message-ID: <166974121830.7750.2703244123651337985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221128065604.1864391-1-yoshihiro.shimoda.uh@renesas.com>

Hello:

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

On Mon, 28 Nov 2022 15:56:04 +0900 you wrote:
> After system resumed on some environment board, the promiscuous mode
> is disabled because the SoC turned off. So, call ravb_set_rx_mode() in
> the ravb_resume() to fix the issue.
> 
> Reported-by: Tho Vu <tho.vu.wh@renesas.com>
> Fixes: 0184165b2f42 ("ravb: add sleep PM suspend/resume support")
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> 
> [...]

Here is the summary with links:
  - [net] net: ethernet: renesas: ravb: Fix promiscuous mode after system resumed
    https://git.kernel.org/netdev/net/c/d66233a312ec

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



      parent reply	other threads:[~2022-11-29 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  6:56 [PATCH net] net: ethernet: renesas: ravb: Fix promiscuous mode after system resumed Yoshihiro Shimoda
2022-11-28  7:24 ` Pavan Chebbi
2022-11-28 18:26 ` Sergey Shtylyov
2022-11-29 17: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=166974121830.7750.2703244123651337985.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=s.shtylyov@omp.ru \
    --cc=tho.vu.wh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox