All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lijun Pan <lijunp213@gmail.com>
To: Cristobal Forno <cforno12@linux.ibm.com>
Cc: netdev@vger.kernel.org, Dany Madden <drt@linux.ibm.com>,
	Sukadev Bhattiprolu <sukadev@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Thomas Falcon <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 14:04:25 -0500	[thread overview]
Message-ID: <CAOhMmr4KjBwH-vU7Z22wpap89=FtwcrYbKah8yvu=eGrnqU76g@mail.gmail.com> (raw)
In-Reply-To: <20210610170835.10190-1-cforno12@linux.ibm.com>

On Thu, Jun 10, 2021 at 12:11 PM Cristobal Forno <cforno12@linux.ibm.com> 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.
>
> Co-developed-by: Thomas Falcon <tlfalcon@linux.ibm.com>
> Signed-off-by: Thomas Falcon <tlfalcon@linux.ibm.com>
> Signed-off-by: Cristobal Forno <cforno12@linux.ibm.com>
>
> ---

Finally, this important feature patch is approved to be sent upstream
after almost one year "censorship" and testing. And the original
author, Tom, is not with the team anymore. I have mixed feelings about
that, but any way,

Acked-by: Lijun Pan <lijunp213@gmail.com>

  reply	other threads:[~2021-06-10 19:04 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 [this message]
2021-06-10 20:36 ` Dany Madden
2021-06-10 21:40 ` patchwork-bot+netdevbpf
  -- 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='CAOhMmr4KjBwH-vU7Z22wpap89=FtwcrYbKah8yvu=eGrnqU76g@mail.gmail.com' \
    --to=lijunp213@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=cforno12@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=drt@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sukadev@linux.ibm.com \
    --cc=tlfalcon@linux.ibm.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.