netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, pabeni@redhat.com, davem@davemloft.net,
	dsahern@kernel.org, mst@redhat.com, jasowang@redhat.com,
	xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	leitao@debian.org, netdev@vger.kernel.org,
	Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v3] net: dqs: introduce IFF_NO_BQL private flag for non-BQL drivers
Date: Thu, 13 Jun 2024 08:02:34 -0700	[thread overview]
Message-ID: <20240613080234.36d61880@kernel.org> (raw)
In-Reply-To: <CAL+tcoAP=Jg3pXO-_46w5CbrGnGVzHf4woqg3bQNCrb8SMhnrw@mail.gmail.com>

On Thu, 13 Jun 2024 22:55:16 +0800 Jason Xing wrote:
> I wonder why the status of this patch was changed to 'Changes
> Requested'? Is there anything else I should adjust?

Sorry to flip the question on you, but do you think the patch should 
be merged as is? Given Jiri is adding BQL support to virtio?

  reply	other threads:[~2024-06-13 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  2:35 [PATCH net-next v3] net: dqs: introduce IFF_NO_BQL private flag for non-BQL drivers Jason Xing
2024-06-13  5:38 ` Jiri Pirko
2024-06-13  6:08   ` Jason Xing
2024-06-13  7:19     ` Jiri Pirko
2024-06-13  7:24       ` Jason Xing
2024-06-13  7:49         ` Jason Xing
2024-06-13  7:51         ` Jiri Pirko
2024-06-13  7:52           ` Jason Xing
2024-06-13  7:56           ` Michael S. Tsirkin
2024-06-13  9:26             ` Jason Xing
2024-06-13 13:08               ` Jason Xing
2024-06-13 13:17               ` Jiri Pirko
2024-06-13 14:11                 ` Jason Xing
2024-06-13 14:34                   ` Jiri Pirko
2024-06-13 14:48                     ` Jason Xing
2024-06-13 14:55 ` Jason Xing
2024-06-13 15:02   ` Jakub Kicinski [this message]
2024-06-13 15:25     ` Eric Dumazet
2024-06-13 15:37       ` Jason Xing
2024-06-13 15:48         ` Eric Dumazet
2024-06-13 16:20           ` Jason Xing
2024-06-13 15:31     ` Jason Xing

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=20240613080234.36d61880@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=leitao@debian.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xuanzhuo@linux.alibaba.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).