All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/7] datastruct: Fix wrong line number
Date: Mon, 19 Nov 2018 17:45:15 -0800	[thread overview]
Message-ID: <20181120014515.GV4170@linux.ibm.com> (raw)
In-Reply-To: <20181120000057.389-1-sj38.park@gmail.com>

On Tue, Nov 20, 2018 at 09:00:51AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good eyes!  I queued and pushed the series, thank you!!!

							Thanx, Paul

> ---
>  datastruct/datastruct.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/datastruct/datastruct.tex b/datastruct/datastruct.tex
> index 1dc2b49..fb8fc20 100644
> --- a/datastruct/datastruct.tex
> +++ b/datastruct/datastruct.tex
> @@ -1549,7 +1549,7 @@ Line~17 conditionally acquires the top-level \co{->ht_lock}, and if
>  this acquisition fails, line~18 returns \co{-EBUSY} to indicate that
>  a resize is already in progress.
>  Otherwise, line~19 picks up a reference to the current hash table,
> -and lines~21-24 allocate a new hash table of the desired size.
> +and lines~20-24 allocate a new hash table of the desired size.
>  If a new set of hash/key functions have been specified, these are
>  used for the new table, otherwise those of the old table are preserved.
>  If line~25 detects memory-allocation failure, line~26 releases \co{->ht_lock}
> -- 
> 2.10.0
> 


      parent reply	other threads:[~2018-11-20 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  0:00 [PATCH 1/7] datastruct: Fix wrong line number SeongJae Park
2018-11-20  0:00 ` [PATCH 2/7] datastruct: Update an outdated footnote SeongJae Park
2018-11-20  0:00 ` [PATCH 3/7] count: Use '\lnref' consistently SeongJae Park
2018-11-20  0:00 ` [PATCH 4/7] toolsoftrade: Fix a typo for function name SeongJae Park
2018-11-20  0:00 ` [PATCH 5/7] toolsoftrade: Use '\co' consistently for volatile keyword SeongJae Park
2018-11-20  0:00 ` [PATCH 6/7] formal/axiomatic: Fix a typo: s/Figure/Listing SeongJae Park
2018-11-20  0:00 ` [PATCH 7/7] formal/axiomatic: Add missed parentheses for 'WRITE_ONCE()' SeongJae Park
2018-11-20  1:45 ` Paul E. McKenney [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=20181120014515.GV4170@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.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.