From: patchwork-bot+netdevbpf@kernel.org
To: Divya Koppera <Divya.Koppera@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, richardcochran@gmail.com,
alexanderduyck@fb.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v6 net-next 0/2] Fixed warnings
Date: Mon, 09 Jan 2023 07:30:16 +0000 [thread overview]
Message-ID: <167324941697.24554.3531681744260203489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230106082905.1159-1-Divya.Koppera@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 6 Jan 2023 13:59:03 +0530 you wrote:
> Fixed warnings related to PTR_ERR and initialization.
>
> Divya Koppera (2):
> net: phy: micrel: Fixed error related to uninitialized symbol ret
> net: phy: micrel: Fix warn: passing zero to PTR_ERR
>
> drivers/net/phy/micrel.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> [...]
Here is the summary with links:
- [v6,net-next,1/2] net: phy: micrel: Fixed error related to uninitialized symbol ret
https://git.kernel.org/netdev/net-next/c/d50ede4f53e1
- [v6,net-next,2/2] net: phy: micrel: Fix warn: passing zero to PTR_ERR
https://git.kernel.org/netdev/net-next/c/3f88d7d1be42
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:[~2023-01-09 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 8:29 [PATCH v6 net-next 0/2] Fixed warnings Divya Koppera
2023-01-06 8:29 ` [PATCH v6 net-next 1/2] net: phy: micrel: Fixed error related to uninitialized symbol ret Divya Koppera
2023-01-06 9:17 ` Arun.Ramadoss
2023-01-06 8:29 ` [PATCH v6 net-next 2/2] net: phy: micrel: Fix warn: passing zero to PTR_ERR Divya Koppera
2023-01-09 7: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=167324941697.24554.3531681744260203489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@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;
as well as URLs for NNTP newsgroup(s).