From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 074736FB9; Thu, 21 Mar 2024 03:38:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710992284; cv=none; b=VTCGkrpj3viDPaa8ZPfpF+199DauzLvJ/4Pw72rILFh3RFmYD2oivXOdDG2omhHXMLPqTLFBCtDBazWHp3k/inOPYFfUeSYS5USip0m4OUo4k3CPV4gLnPt9v1/7+K5e96XYRAvyMssOZYoo+N5JTUtJHYLTaZgujPY6Gf2vJYY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710992284; c=relaxed/simple; bh=Fas2GPcJqSFKc4TRosyOnXTJyUpVpqqdoA8FKsHNKkA=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=t2TgVwHavW4s4ObEbGTzLYgqhL6a06gNe6pYp5ef41Mz6/JCsNuFH7gIgad7q7LDIVVM9PKFNPJA4Kx6VwEEia0jn3KeHDvKtuUQ/Pzb2J7H1fDiC/g+9GA/wrOkKGmH8DQF/JIxwXXjcddCQ4JFpvZU8CvSDVXmdRLAwrDrhTA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=feTiWOad; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="feTiWOad" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F379C433C7; Thu, 21 Mar 2024 03:38:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1710992283; bh=Fas2GPcJqSFKc4TRosyOnXTJyUpVpqqdoA8FKsHNKkA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=feTiWOadsvmjA6vBTMbtF62EasYWdZd9ARTvh9kiSSi9JdbveqtIHAiu8v9rJeaqF 9c5GXMIaQvEl4WHgilK+lCphWPmlHADTKkWROZk/tLT9bYk8SXz8M8a9RvpGL+SLZk htGF3LJZhjDiHWNRO8WAFqyecAct5WO1VuZucheNZqRVWKg6Ve5dSbNSqUtSl34mNQ xH/gea+MYw+DQ3anCel4k5mim9kW5Sen4m1boLtrlBuFlwI0Rhw5C5pzdOYIi9fagh coJTutsn1kz9p2f+bsJTx5nBpg67du+EvjHc6o1dkM0MHOHAbZaL9iW3x3l6VoKEv1 XRVQTvMKEVLxQ== Date: Wed, 20 Mar 2024 20:38:01 -0700 From: Jakub Kicinski To: Xuan Zhuo Cc: Paolo Abeni , netdev@vger.kernel.org, "David S. Miller" , Eric Dumazet , "Michael S. Tsirkin" , Jason Wang , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , Stanislav Fomichev , Amritha Nambiar , Larysa Zaremba , Sridhar Samudrala , Maciej Fijalkowski , virtualization@lists.linux.dev, bpf@vger.kernel.org, Jiri Pirko Subject: Re: [PATCH net-next v5 0/9] virtio-net: support device stats Message-ID: <20240320203801.5950fb1d@kernel.org> In-Reply-To: <1710921861.9268863-1-xuanzhuo@linux.alibaba.com> References: <20240318110602.37166-1-xuanzhuo@linux.alibaba.com> <1710762818.1520293-1-xuanzhuo@linux.alibaba.com> <316ea06417279a45d2d54bf4cc4afd2d775b419a.camel@redhat.com> <1710921861.9268863-1-xuanzhuo@linux.alibaba.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 20 Mar 2024 16:04:21 +0800 Xuan Zhuo wrote: > 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 > window is open or closed? This causes the title of our patch sets to keep > changing. Is switching between RFC and PATCH causing issues? Should be a simple modification to the git format-patch argument. But perhaps your workload is different than mine. The merge window is only 2 weeks every 10 weeks, it's not changing often, I don't think.