DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Vamsi Krishna <vattunuru@marvell.com>
Cc: jerinj@marvell.com, dev@dpdk.org
Subject: Re: [PATCH v3 1/1] net/octeon_ep: add device removal event callback
Date: Thu, 3 Oct 2024 13:36:02 +0530	[thread overview]
Message-ID: <CALBAE1Po89_WJgqr7-rz0PU7N8iicN7PAq6tQY3H98UOZ9ZtNw@mail.gmail.com> (raw)
In-Reply-To: <20241001083837.1308452-1-vattunuru@marvell.com>

On Tue, Oct 1, 2024 at 2:08 PM Vamsi Krishna <vattunuru@marvell.com> wrote:
>
> From: Vamsi Attunuru <vattunuru@marvell.com>
>
> Adds an event callback to catch any device removal
> event occurred during driver probe. This callback helps
> in terminating the execution if there is any device removal
> event during the driver probe.
>
> Also moved global register configuration into dev_configure()
> routine and also validates register reads for any invalid
> return values from hardware during driver probe.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>

Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-main. Thanks

    net/octeon_ep: handle device removal on probe

    Adds an event callback to catch any device removal
    event occurred during driver probe. This callback helps
    in terminating the execution if there is any device removal
    event during the driver probe.

    Also moved global register configuration into dev_configure()
    routine and also validates register reads for any invalid
    return values from hardware during driver probe.

    Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>

      reply	other threads:[~2024-10-03  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  5:32 [PATCH] " Vamsi Krishna
2024-09-19 18:18 ` Jerin Jacob
2024-09-20  3:48   ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-09-20  4:43 ` [PATCH v2 1/1] " Vamsi Krishna
2024-10-01  8:17   ` Jerin Jacob
2024-10-01  8:38   ` [PATCH v3 " Vamsi Krishna
2024-10-03  8:06     ` Jerin Jacob [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=CALBAE1Po89_WJgqr7-rz0PU7N8iicN7PAq6tQY3H98UOZ9ZtNw@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=vattunuru@marvell.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).