git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Kreimer <algonell@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cbtree: fix a typo
Date: Mon, 16 Sep 2024 12:52:30 +0300	[thread overview]
Message-ID: <Zuf_3mNRm3KuQxlV@void.void> (raw)
In-Reply-To: <Zufef70mfdUwSwnY@pks.im>

On Mon, Sep 16, 2024 at 09:30:07AM +0200, Patrick Steinhardt wrote:
> On Mon, Sep 16, 2024 at 02:05:22AM +0300, Andrew Kreimer wrote:
> > Fix a typo in comments.
> > 
> > Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> 
> Thanks for these fixes, all three of them look good to me. For future
> such patch series I'd recommend to send a single series that combines
> such related fixes. It makes it a bit easier to keep track of these
> similar patches and review them in one go.
> 

Understood.

> > ---
> >  cbtree.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/cbtree.c b/cbtree.c
> > index c1cc30a5dc..cf8cf75b89 100644
> > --- a/cbtree.c
> > +++ b/cbtree.c
> > @@ -12,7 +12,7 @@ static struct cb_node *cb_node_of(const void *p)
> >  	return (struct cb_node *)((uintptr_t)p - 1);
> >  }
> >  
> > -/* locate the best match, does not do a final comparision */
> > +/* locate the best match, does not do a final comparison */
> >  static struct cb_node *cb_internal_best_match(struct cb_node *p,
> >  					const uint8_t *k, size_t klen)
> >  {
> 
> We might convert this to be a proper sentence while at it, namely
> s/locate/Locate/ and s/comparison/&./. But no need to reroll this patch
> for that, as your change is a strict improvement by itself already.
> 
> Thanks!
> 
> Patrick

Thank you!

  reply	other threads:[~2024-09-16  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15 23:05 [PATCH] cbtree: fix a typo Andrew Kreimer
2024-09-16  7:30 ` Patrick Steinhardt
2024-09-16  9:52   ` Andrew Kreimer [this message]
2024-09-16 17:50     ` Junio C Hamano

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=Zuf_3mNRm3KuQxlV@void.void \
    --to=algonell@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).