All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ric Li <ming3.li@intel.com>, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	dev@dpdk.org, dev@dpdk.org, roretzla@linux.microsoft.com
Subject: Re: [PATCH v4] windows/virt2phys: fix block MDL not updated
Date: Wed, 20 Nov 2024 13:03:05 +0100	[thread overview]
Message-ID: <3342402.G96rZvMJ2N@thomas> (raw)
In-Reply-To: <20241016093205.785ce20f@sovereign>

16/10/2024 08:32, Dmitry Kozlyuk:
> 2024-10-15 16:04 (UTC-0700), Stephen Hemminger:
> > This looks ok, but I know nothing about windows drivers.
> > Could we get a review by Dmitry?
> 
> v3 got Reviewed-by almost a year ago, v4 only did a bit of renaming:
> 
> 	http://inbox.dpdk.org/dev/20231130071001.4c7931c8@sovereign/
> 
> There were no other Windows patches to dpdk-kmods, so it still applies.

Added your Reviewed-by, and applied, thanks.



  reply	other threads:[~2024-11-20 12:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  8:22 [PATCH] windows/virt2phys: fix block MDL not updated Ric Li
2023-09-11 13:09 ` [PATCH v2] " Ric Li
2023-09-11 21:50   ` Dmitry Kozlyuk
2023-09-12 11:13     ` Li, Ming3
2023-09-12 11:17       ` [PATCH v3] " Ric Li
2023-11-27  1:31         ` Li, Ming3
2023-11-30  4:10         ` Dmitry Kozlyuk
2023-12-04 10:22           ` [PATCH v4] " Ric Li
2023-12-04 10:32           ` Ric Li
2024-10-15 23:04             ` Stephen Hemminger
2024-10-16  6:32               ` Dmitry Kozlyuk
2024-11-20 12:03                 ` Thomas Monjalon [this message]
2023-09-12 12:18       ` [PATCH v2] " Dmitry Kozlyuk

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=3342402.G96rZvMJ2N@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=ming3.li@intel.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    /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.