mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] rbtree.txt: fix typo in cached rbtree section
Date: Sat, 2 Dec 2017 04:35:26 -0800	[thread overview]
Message-ID: <20171202123526.olzjs7ukmt55i4lp@linux-n805> (raw)
In-Reply-To: <20171201235223.GX692@shells.gnugeneration.com>

I'm happy to ack your patch but you have to send it correctly.
You are missing a changelog (although it ought to be small due
to the trivial change) as well as you SoB tag. Please consult
Documentation/process/submitting-patches.rst.

You also need to Cc akpm as he routes such areas to Linus.

Thanks,
Davidlohr

On Fri, 01 Dec 2017, Vito Caputo wrote:

>---
> Documentation/rbtree.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/Documentation/rbtree.txt b/Documentation/rbtree.txt
>index c42a21b99046..3a4c23bc90b2 100644
>--- a/Documentation/rbtree.txt
>+++ b/Documentation/rbtree.txt
>@@ -197,9 +197,9 @@ Cached rbtrees
> --------------
>
> Computing the leftmost (smallest) node is quite a common task for binary
>-search trees, such as for traversals or users relying on a the particular
>-order for their own logic. To this end, users can use 'struct rb_root_cached'
>-to optimize O(logN) rb_first() calls to a simple pointer fetch avoiding
>+search trees, such as for traversals or users relying on a particular order
>+for their own logic. To this end, users can use 'struct rb_root_cached' to
>+optimize O(logN) rb_first() calls to a simple pointer fetch avoiding
> potentially expensive tree iterations. This is done at negligible runtime
> overhead for maintanence; albeit larger memory footprint.
>
>-- 
>2.11.0
>

      reply	other threads:[~2017-12-02 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 23:52 Vito Caputo
2017-12-02 12:35 ` Davidlohr Bueso [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=20171202123526.olzjs7ukmt55i4lp@linux-n805 \
    --to=dave@stgolabs.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vcaputo@pengaru.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome