From: patchwork-bot+netdevbpf@kernel•org
To: Cristobal Forno <cforno12@linux•ibm.com>
Cc: netdev@vger•kernel.org, drt@linux•ibm.com, sukadev@linux•ibm.com,
mpe@ellerman•id.au, benh@kernel•crashing.org, paulus@samba•org,
davem@davemloft•net, kuba@kernel•org, tlfalcon@linux•ibm.com
Subject: Re: [PATCH, net-next, v2] ibmvnic: Allow device probe if the device is not ready at boot
Date: Thu, 10 Jun 2021 21:40:03 +0000 [thread overview]
Message-ID: <162336120392.23488.10694134296837837250.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210610170835.10190-1-cforno12@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 10 Jun 2021 11:08:35 -0600 you wrote:
> Allow the device to be initialized at a later time if
> it is not available at boot. The device will be allowed to probe but
> will be given a "down" state. After completing device probe and
> registering the net device, the driver will await an interrupt signal
> from its partner device, indicating that it is ready for boot. The
> driver will schedule a work event to perform the necessary procedure
> and begin operation.
>
> [...]
Here is the summary with links:
- [net-next,v2] ibmvnic: Allow device probe if the device is not ready at boot
https://git.kernel.org/netdev/net-next/c/53f8b1b25419
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-06-10 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 17:08 [PATCH, net-next, v2] ibmvnic: Allow device probe if the device is not ready at boot Cristobal Forno
2021-06-10 19:04 ` Lijun Pan
2021-06-10 20:36 ` Dany Madden
2021-06-10 21:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-07 17:47 Cristobal Forno
2021-05-07 18:02 ` Lijun Pan
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=162336120392.23488.10694134296837837250.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=cforno12@linux$(echo .)ibm.com \
--cc=davem@davemloft$(echo .)net \
--cc=drt@linux$(echo .)ibm.com \
--cc=kuba@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulus@samba$(echo .)org \
--cc=sukadev@linux$(echo .)ibm.com \
--cc=tlfalcon@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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