All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Juran <jjuran@gmail.com>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Greg Ungerer <gerg@linux-m68k.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k: coldfire: fix typo "reseting" in comment
Date: Mon, 21 Sep 2026 18:52:52 -0400	[thread overview]
Message-ID: <C647EC67-4CAD-480C-9A78-EF5A2C2D718F@gmail.com> (raw)
In-Reply-To: <20260907091544.36558-1-hemanth.selam@gmail.com>

On Sep 7, 2026, at 5:15 AM, Hemanth Selam <hemanth.selam@gmail.com> wrote:

> On Sun, Sep 06, 2026 at 02:46:04AM -0400, Josh Juran wrote:
> 
>> What about the human reviewing its output?  Or am I misunderstanding
>> the meaning of "Signed-off-by"?
> 
> You are not misunderstanding it.  My Signed-off-by certifies the DCO,
> but sending the patch also means I am answerable for what is in it, and
> on this one I did not look hard enough.

Thank you for accepting my question on its merits (despite the rhetorical barb I attached to it) and answering thoughtfully.  I could not have asked for more humility than you’ve shown in your reply.

> The wider lesson I am taking from this is that a large series does not
> get to be reviewed in bulk.  Each patch has to be read on its own, in
> context, before it goes out, and that is what I will be doing for the
> rest of this work.

Again, I couldn’t ask for more than that.  Thank you.

> Thanks for pushing on it rather than letting it through.

You’re welcome.  Thanks for listening.

Peace,
Josh


      reply	other threads:[~2026-09-21 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 11:23 [PATCH] m68k: coldfire: fix typo "reseting" in comment Hemanth Selam
2026-09-06  6:40 ` Josh Juran
2026-09-06  6:43   ` John Paul Adrian Glaubitz
2026-09-06  6:46     ` Josh Juran
2026-09-07  9:15       ` Hemanth Selam
2026-09-21 22:52         ` Josh Juran [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=C647EC67-4CAD-480C-9A78-EF5A2C2D718F@gmail.com \
    --to=jjuran@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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.