From: Dave Marquardt <davemarq@linux.ibm.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: tools@kernel.org, Tyrel Datwyler <tyreld@linux.ibm.com>
Subject: Re: [Tyrel Datwyler] Re: [PATCH v2 6/7] ibmvfc: register and use asynchronous sub-queue
Date: Tue, 16 Jun 2026 07:52:36 -0500 [thread overview]
Message-ID: <87cxxqodez.fsf@linux.ibm.com> (raw)
In-Reply-To: <20260615-smiling-kelpie-of-temperance-4dd61b@meerkat> (Konstantin Ryabitsev's message of "Mon, 15 Jun 2026 17:51:39 -0400")
Konstantin Ryabitsev <mricon@kernel.org> writes:
> On Mon, Jun 15, 2026 at 04:14:48PM -0500, Dave Marquardt wrote:
>>
>> Hi Konstantin. I'm using b4 to send patch series. I get these comments
>> about not having a Signed-off-by: tag. Should the tag be added by b4? Or
>> should the patch attestation be enough?
>
> That's not really the right way to put it. Different projects will have
> different DCO requirements and it's not up to b4 to enforce the presence of
> trailers. It's not the same as patch attestation -- the attestation's job is
> to mechanically attest that the patches haven't been tampered since they left
> your system. The Signed-off-by: trailer is more about the actual code you're
> committing.
>
>> I do notice that "b4 prep --check" flags some patches as missing the
>> Signed-off-by: tag, particularly when I've chosen to not fix some
>> warnings.
>
> It's speaking to you, then! :)
>
> You can either manually run all commits with -s (which is what I do), or you
> can set up a hook to do that for you automatically -- but since it's supposed
> to be a deliberate action by the committer, I recommend just always
> remembering to add that little "-s" after "git commit".
Thanks. I searched and searched the b4 documentation, and now, from your
explanation, understand why I don't see anything about Signed-off-by:
when submitting a patch series. Would it be worth adding something to
the manual? (Yes, if so, I'm volunteering :) )
-Dave
prev parent reply other threads:[~2026-06-16 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 21:14 [Tyrel Datwyler] Re: [PATCH v2 6/7] ibmvfc: register and use asynchronous sub-queue Dave Marquardt
2026-06-15 21:51 ` Konstantin Ryabitsev
2026-06-16 12:52 ` Dave Marquardt [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=87cxxqodez.fsf@linux.ibm.com \
--to=davemarq@linux.ibm.com \
--cc=mricon@kernel.org \
--cc=tools@kernel.org \
--cc=tyreld@linux.ibm.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 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.