From: patchwork-bot+netdevbpf@kernel.org
To: Peter Geis <pgwipeout@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, kuba@kernel.org, nathan@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH v3 0/2] fixes for yt8511 phy driver
Date: Sun, 30 May 2021 21:30:03 +0000 [thread overview]
Message-ID: <162241020386.28062.1219688691635725746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210529110556.202531-1-pgwipeout@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 29 May 2021 07:05:54 -0400 you wrote:
> The Intel clang bot caught a few uninitialized variables in the new
> Motorcomm driver. While investigating the issue, it was found that the
> driver would have unintended effects when used in an unsupported mode.
>
> Fixed the uninitialized ret variable and abort loading the driver in
> unsupported modes.
>
> [...]
Here is the summary with links:
- [v3,1/2] net: phy: fix yt8511 clang uninitialized variable warning
https://git.kernel.org/netdev/net-next/c/546d6bad18c0
- [v3,2/2] net: phy: abort loading yt8511 driver in unsupported modes
https://git.kernel.org/netdev/net-next/c/0cc8bddb5b06
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-30 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 11:05 [PATCH v3 0/2] fixes for yt8511 phy driver Peter Geis
2021-05-29 11:05 ` [PATCH v3 1/2] net: phy: fix yt8511 clang uninitialized variable warning Peter Geis
2021-05-29 11:05 ` [PATCH v3 2/2] net: phy: abort loading yt8511 driver in unsupported modes Peter Geis
2021-05-30 21:30 ` 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=162241020386.28062.1219688691635725746.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pgwipeout@gmail.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