Wed, Mar 20, 2024 at 09:04:21AM CET, xuanzhuo@xxxxxxxxxxxxxxxxx wrote: >On Tue, 19 Mar 2024 11:12:23 +0100, Paolo Abeni <pabeni@xxxxxxxxxx> wrote: >> On Mon, 2024-03-18 at 13:19 +0100, Jiri Pirko wrote: >> > Mon, Mar 18, 2024 at 12:53:38PM CET, xuanzhuo@xxxxxxxxxxxxxxxxx wrote: >> > > On Mon, 18 Mar 2024 12:52:18 +0100, Jiri Pirko <jiri@xxxxxxxxxxx> wrote: >> > > > Mon, Mar 18, 2024 at 12:05:53PM CET, xuanzhuo@xxxxxxxxxxxxxxxxx wrote: >> > > > > As the spec: >> > > > > >> > > > > https://github.com/oasis-tcs/virtio-spec/commit/42f389989823039724f95bbbd243291ab0064f82 >> > > > > >> > > > > The virtio net supports to get device stats. >> > > > > >> > > > > Please review. >> > > > >> > > > net-next is closed. Please resubmit next week. >> > > >> > > >> > > For review. >> > >> > RFC, or wait. >> >> @Xuan, please note that you received exactly the same feedback on your >> previous submission, a few days ago. While I do understand the legit >> interest in reviews, ignoring explicit feedback tend to bring no >> feedback at all. > >Sorry. > >I have a question regarding the workflow for feature discussions. If we >consistently engage in discussions about a particular feature, this may result >in the submission of multiple patch sets. In light of this, should we modify the >usage of "PATCH" or "RFC" in our submissions depending on whether the merge No, just wait 2 weeks, simple. >window is open or closed? This causes the title of our patch sets to keep >changing. > >Or I miss something. > > >Thanks. > > >> >> Paolo >>
