From: Si-Wei Liu <si-wei.liu@oracle.com>
To: David Ahern <dsahern@kernel.org>
Cc: allen.hubbe@amd.com, drivers@pensando.io, jasowang@redhat.com,
mst@redhat.com, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
shannon.nelson@amd.com
Subject: Re: [PATCH] vdpa: consume device_features parameter
Date: Fri, 8 Sep 2023 11:37:58 -0700 [thread overview]
Message-ID: <b4014822-48af-ea9e-853f-0a0af3fc47ed@oracle.com> (raw)
In-Reply-To: <060ee8d4-3b78-c360-ac36-3f6609a5da89@kernel.org>
On 9/7/2023 5:07 PM, David Ahern wrote:
> On 9/7/23 2:41 PM, Si-Wei Liu wrote:
>> Hi David,
>>
>> Why this patch doesn't get picked in the last 4 months? Maybe the
>> subject is not clear, but this is an iproute2 patch. Would it be
>> possible to merge at your earliest convenience?
>>
>> PS, adding my R-b to the patch.
>>
> It got marked "Not applicable":
> https://patchwork.kernel.org/project/netdevbpf/patch/29db10bca7e5ef6b1137282292660fc337a4323a.1683907102.git.allen.hubbe@amd.com/
>
> Resend the patch with any reviewed by tags and be sure to cc me.
>
Just out of my own curiosity, the patch is not applicable simply because
the iproute2 was missing from the subject, or the code base somehow got
changed that isn't aligned with the patch any more?
Thanks,
-Siwei
next prev parent reply other threads:[~2023-09-08 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 16:41 [PATCH] vdpa: consume device_features parameter Shannon Nelson
2023-05-17 5:56 ` Jason Wang
2023-05-18 6:51 ` Eugenio Perez Martin
2023-09-07 20:41 ` Si-Wei Liu
2023-09-07 23:02 ` Nelson, Shannon
2023-09-08 0:07 ` David Ahern
2023-09-08 18:37 ` Si-Wei Liu [this message]
2023-09-09 20:36 ` David Ahern
2023-09-12 0:33 ` Si-Wei Liu
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=b4014822-48af-ea9e-853f-0a0af3fc47ed@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=allen.hubbe@amd.com \
--cc=drivers@pensando.io \
--cc=dsahern@kernel.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.com \
--cc=virtualization@lists.linux-foundation.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 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).