[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <175846968308.4354.2923659909996682902@lazor>
Date: Sun, 21 Sep 2025 08:48:03 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Daniel Almeida <daniel.almeida@...labora.com>
Cc: Boqun Feng <boqun.feng@...il.com>, Michael Turquette <mturquette@...libre.com>, Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>, Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, Rafael J. Wysocki <rafael@...nel.org>, Viresh Kumar <viresh.kumar@...aro.org>, linux-clk@...r.kernel.org, rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2 1/2] rust: clk: implement Send and Sync
Quoting Daniel Almeida (2025-09-20 03:33:07)
> Hi Stephen,
>
> […]
>
> >>
> >> You have to include your SOB when submitting patches from others.
> >>
> >> This is something I tend to forget often, so I made sure it was there. The
> >> order may be indeed off though.
> >
> > Yes the order is wrong. The first SoB should be the commit author.
>
> Do you want me to send a new version, or do you prefer fixing this before applying?
>
> For trivial changes some maintainers prefer the latter to reduce the amount of noise.
>
You can send another round. I'm waiting to see if anyone will review the
second patch. Maybe sending another round will prompt a review.
Powered by blists - more mailing lists