From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Mikhaylov <i.mikhaylov@yadro.com>
Cc: netdev@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, kuba@kernel.org,
sam@mendozajonas.com, davem@davemloft.net
Subject: Re: [PATCH v2 0/3] net/ncsi: Add NCSI Intel OEM command to keep PHY link up
Date: Thu, 08 Jul 2021 21:20:04 +0000 [thread overview]
Message-ID: <162577920431.534.17888318132713618711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210708122754.555846-1-i.mikhaylov@yadro.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 8 Jul 2021 15:27:51 +0300 you wrote:
> Add NCSI Intel OEM command to keep PHY link up and prevents any channel
> resets during the host load on i210. Also includes dummy response handler for
> Intel manufacturer id.
>
> Changes from v1:
> 1. sparse fixes about casts
> 2. put it after ncsi_dev_state_probe_cis instead of
> ncsi_dev_state_probe_channel because sometimes channel is not ready
> after it
> 3. inl -> intel
>
> [...]
Here is the summary with links:
- [v2,1/3] net/ncsi: fix restricted cast warning of sparse
https://git.kernel.org/netdev/net/c/27fa107d3b8d
- [v2,2/3] net/ncsi: add NCSI Intel OEM command to keep PHY up
https://git.kernel.org/netdev/net/c/abd2fddc94a6
- [v2,3/3] net/ncsi: add dummy response handler for Intel boards
https://git.kernel.org/netdev/net/c/163f5de509a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-07-12 2:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 12:27 [PATCH v2 0/3] net/ncsi: Add NCSI Intel OEM command to keep PHY link up Ivan Mikhaylov
2021-07-08 12:27 ` [PATCH v2 1/3] net/ncsi: fix restricted cast warning of sparse Ivan Mikhaylov
2021-07-12 9:09 ` Joel Stanley
2021-07-13 9:08 ` Ivan Mikhaylov
2021-07-08 12:27 ` [PATCH v2 2/3] net/ncsi: add NCSI Intel OEM command to keep PHY up Ivan Mikhaylov
2021-07-12 10:01 ` Joel Stanley
2021-07-12 19:32 ` Eddie James
2021-07-13 10:16 ` Ivan Mikhaylov
2021-07-08 12:27 ` [PATCH v2 3/3] net/ncsi: add dummy response handler for Intel boards Ivan Mikhaylov
2021-07-12 10:03 ` Joel Stanley
2021-07-13 9:42 ` Ivan Mikhaylov
2021-07-20 9:41 ` Paul Fertser
2021-07-20 13:21 ` Ivan Mikhaylov
2021-07-20 13:29 ` Paul Fertser
2021-07-08 21:20 ` patchwork-bot+netdevbpf [this message]
2021-07-20 9:53 ` [PATCH v2 0/3] net/ncsi: Add NCSI Intel OEM command to keep PHY link up Paul Fertser
2021-07-20 14:00 ` Ivan Mikhaylov
2021-07-20 14:16 ` Paul Fertser
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=162577920431.534.17888318132713618711.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=i.mikhaylov@yadro.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sam@mendozajonas.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).