All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
	joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
	mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: stmmac: enable platform specific safety features
Date: Wed, 02 Jun 2021 00:10:08 +0000	[thread overview]
Message-ID: <162259260848.22595.3435009042583708673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210601135235.1058841-1-vee.khee.wong@linux.intel.com>

Hello:

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

On Tue,  1 Jun 2021 21:52:35 +0800 you wrote:
> On Intel platforms, not all safety features are enabled on the hardware.
> The current implementation enable all safety features by default. This
> will cause mass error and warning printouts after the module is loaded.
> 
> Introduce platform specific safety features flag to enable or disable
> each safety features.
> 
> [...]

Here is the summary with links:
  - [net-next,1/1] net: stmmac: enable platform specific safety features
    https://git.kernel.org/netdev/net-next/c/5ac712dcdfef

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Wong Vee Khee <vee.khee.wong@linux.intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
	joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
	mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/1] net: stmmac: enable platform specific safety features
Date: Wed, 02 Jun 2021 00:10:08 +0000	[thread overview]
Message-ID: <162259260848.22595.3435009042583708673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210601135235.1058841-1-vee.khee.wong@linux.intel.com>

Hello:

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

On Tue,  1 Jun 2021 21:52:35 +0800 you wrote:
> On Intel platforms, not all safety features are enabled on the hardware.
> The current implementation enable all safety features by default. This
> will cause mass error and warning printouts after the module is loaded.
> 
> Introduce platform specific safety features flag to enable or disable
> each safety features.
> 
> [...]

Here is the summary with links:
  - [net-next,1/1] net: stmmac: enable platform specific safety features
    https://git.kernel.org/netdev/net-next/c/5ac712dcdfef

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



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-06-02  0:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 13:52 [PATCH net-next 1/1] net: stmmac: enable platform specific safety features Wong Vee Khee
2021-06-01 13:52 ` Wong Vee Khee
2021-06-01 22:11 ` Andrew Lunn
2021-06-01 22:11   ` Andrew Lunn
2021-06-01 22:53   ` Wong Vee Khee
2021-06-01 22:53     ` Wong Vee Khee
2021-06-02  2:28     ` Andrew Lunn
2021-06-02  2:28       ` Andrew Lunn
2021-06-02  0:10 ` patchwork-bot+netdevbpf [this message]
2021-06-02  0:10   ` patchwork-bot+netdevbpf

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=162259260848.22595.3435009042583708673.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=davem@davemloft.net \
    --cc=joabreu@synopsys.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=vee.khee.wong@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.