All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	SeongJae Park <sj38.park@gmail.com>,
	perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 1/7] formal/spinhint: Don't use \qco{} for long message
Date: Sat, 29 Apr 2023 16:40:02 -0700	[thread overview]
Message-ID: <20230429234002.18552-1-sj@kernel.org> (raw)
In-Reply-To: <8e1a521a-7d95-ebf6-e783-6a15c01a43a5@gmail.com>

On Sun, 30 Apr 2023 08:05:30 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:

> \qco{} is intended to be used for short snippets and suppresses line
> breaks in its argument by using \nbco{} in its definition.
> Commit 88fd12717c61 ("formal/spinhint: Use \qco{} instead of``\co{}''")
> applied \qco{} for a long error message.
> It causes "Underfull \hbox" of large badness preceding it.
> 
> In perfbook-1c.log and perfbook-eb.log:
> 
>     Underfull \hbox (badness 10000) in paragraph at lines 277--281
>     []\T1/ntxtlf/m/n/10 (+20) If you see a mes-sage from [][][][] say-ing:
>      []
> 
> In perfbook.log:
> 
>     Underfull \hbox (badness 2495) in paragraph at lines 277--281
>     []\T1/ntxtlf/m/n/10 (+20) If you see a mes-sage from [][][][] say-ing:
>      []
> 
> Revert the change and permit line breaks in the middle of the quoted
> message.

Thank you for fixing this, Akira!

> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Cc: SeongJae Park <sj38.park@gmail.com>

Reviewed-by: SeongJae Park <sj38.park@gmail.com>


Thanks,
SJ

> ---
>  formal/spinhint.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/formal/spinhint.tex b/formal/spinhint.tex
> index 9bb5f5749470..16764aef8620 100644
> --- a/formal/spinhint.tex
> +++ b/formal/spinhint.tex
> @@ -275,7 +275,7 @@ Given a source file \path{qrcu.spin}, one can use the following commands:
>  	10.5\,GB of memory even with the \co{-DCOLLAPSE} flag.
>  
>  	If you see a message from \co{./pan} saying:
> -	\qco{error: max search depth too small}, you need to increase
> +	``\co{error: max search depth too small}'', you need to increase
>  	the maximum depth by a \co{-mN} option for a complete search.
>  	The default is \co{-m10000}.
>  
> -- 
> 2.25.1
> 
> 

  reply	other threads:[~2023-04-29 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 23:01 [PATCH -perfbook 0/7] Collection of minor fixes and updates Akira Yokosawa
2023-04-29 23:05 ` [PATCH -perfbook 1/7] formal/spinhint: Don't use \qco{} for long message Akira Yokosawa
2023-04-29 23:40   ` SeongJae Park [this message]
2023-04-29 23:07 ` [PATCH -perfbook 2/7] formal/ppcmem: Use \qco{} as intended Akira Yokosawa
2023-04-29 23:41   ` SeongJae Park
2023-04-30  0:26     ` Paul E. McKenney
2023-04-29 23:08 ` [PATCH -perfbook 3/7] Add acronyms of LKMM and KCSAN Akira Yokosawa
2023-04-29 23:13 ` [PATCH -perfbook 4/7] CodeSamples/count: Adjust coding style Akira Yokosawa
2023-04-29 23:16 ` [PATCH -perfbook 5/7] count: Adjust scaling factor of Listing 5.18 Akira Yokosawa
2023-04-29 23:22 ` [PATCH -perfbook 6/7] Tweak TOC width params Akira Yokosawa
2023-04-30  0:30   ` Paul E. McKenney
2023-04-29 23:23 ` [PATCH -perfbook 7/7] precheck.sh: Export LC_TIME Akira Yokosawa

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=20230429234002.18552-1-sj@kernel.org \
    --to=sj38.park@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.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.