All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hsiu Che Yu <yu.whisper.personal@gmail.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: "Hsiu Che Yu" <yu.whisper.personal@gmail.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Lorenzo Stoakes" <ljs@kernel.org>,
	"Vlastimil Babka" <vbabka@kernel.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Uladzislau Rezki" <urezki@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: alloc: add doc test for `Vec::from_elem`
Date: Mon, 27 Apr 2026 12:08:30 +0800	[thread overview]
Message-ID: <69eee141.170a0220.269ea4.eb23@mx.google.com> (raw)
In-Reply-To: <DI3417MXPI5F.1DMTUFZULXTUF@nvidia.com>

On Sun, Apr 26, 2026 at 10:11:01PM +0900, Alexandre Courbot wrote:
>I don't think there is any hard rule, but usually a patch series implies
>a dependency between the patches, i.e. patch 2 cannot build without
>patch 1. For what you sent so far this is not the case, so separate
>patches is fine and maybe even preferable as they can be applied
>individually whereas maintainers tend to consider series as "all or
>nothing" (there are exceptions of course).

I think I now understand the distinction between a patch series and
individual patches. For independent changes, I'll just send them as
separate patches.

On Sun, Apr 26, 2026 at 10:11:01PM +0900, Alexandre Courbot wrote:
>No worries. If I may recommend b4 [1] for managing your patch series, it
>ususally just does the right thing for you.
>
>[1] https://b4.docs.kernel.org/en/latest/

I've just started using b4, and it has been really helpful — it takes
care of a lot of things that previously required juggling multiple tools.

Thanks,
Hsiu

      reply	other threads:[~2026-04-27  4:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26  3:46 [PATCH] rust: alloc: add doc test for `Vec::from_elem` Hsiu Che Yu
2026-04-26  4:05 ` Alexandre Courbot
2026-04-26  4:27   ` Hsiu Che Yu
2026-04-26 13:11     ` Alexandre Courbot
2026-04-27  4:08       ` Hsiu Che Yu [this message]

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=69eee141.170a0220.269ea4.eb23@mx.google.com \
    --to=yu.whisper.personal@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=urezki@gmail.com \
    --cc=vbabka@kernel.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.