public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line
Date: Mon, 27 Nov 2017 06:34:06 +0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1711270732550.2369@hadrien> (raw)
In-Reply-To: <ec39f4f5-cfab-a184-0f27-7f0172e2984f@deltatee.com>



On Sun, 26 Nov 2017, Logan Gunthorpe wrote:

>
>
> On 26/11/17 11:11 PM, Julia Lawall wrote:
> > I don't have a different warning if the string ends in a space.  I have a
> > different warning when one possible control-flow path is fine and another
> > control-flow path is not.  The space thing relates to guessing whether
> > some other printing API function needs a newline or not.
>
> Understood. For checkpatch, there only is warnings (of various types)
> and I was referring to the guessing you mentioned. So if we see that a
> call has no new line and the following one isn't a KERN_CONT, then based
> on whether there's a space or not we potentially could have one of two
> warnings:
>
> WARNING: Log messages should end in a new line (\n)
>
> or
>
> WARNING: Given that your log message ends in a space and not a new line,
> did you maybe mean to put a KERN_CONT or pr_cont somewhere in there?? By
> the way, though, KERN_CONT use is discouraged and will create its own
> warning when you fix it.

It would probably be better not to mention the KERN_CONT possibility at
all.

julia

  reply	other threads:[~2017-11-27  6:34 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26  5:40 [PATCH v2] checkpatch: Add a warning for log messages that don't end in a new line Logan Gunthorpe
2017-11-26  5:51 ` Julia Lawall
2017-11-26  6:01   ` Joe Perches
2017-11-26 17:38     ` Logan Gunthorpe
2017-11-26 22:29       ` Joe Perches
     [not found]         ` <alpine.DEB.2.20.1711262334370.2111@hadrien>
2017-11-27  1:12           ` Joe Perches
2017-11-27  6:08             ` Julia Lawall
2017-11-27  9:25               ` Joe Perches
2017-11-27  9:32                 ` Julia Lawall
2017-11-27  9:42                   ` Joe Perches
2017-11-27 17:07                 ` Logan Gunthorpe
2017-11-27 17:26                   ` Joe Perches
2017-11-27 17:33                     ` Logan Gunthorpe
2017-11-27 17:41                       ` Joe Perches
2017-11-27 17:42                         ` Logan Gunthorpe
2017-11-27  4:00         ` Logan Gunthorpe
2017-11-27  6:11           ` Julia Lawall
2017-11-27  6:27             ` Logan Gunthorpe
2017-11-27  6:34               ` Julia Lawall [this message]
2017-11-27  6:40                 ` Logan Gunthorpe
2017-11-27  8:28                   ` Joe Perches
2017-11-27  8:52                     ` Julia Lawall
2017-11-27  9:06                       ` Joe Perches
2017-11-27 16:40                       ` Logan Gunthorpe
2017-11-27 17:20                     ` Logan Gunthorpe
2017-11-27 17:28                       ` Joe Perches
2017-11-27 17:35                         ` Logan Gunthorpe
2017-11-27 17:42                           ` Joe Perches
2017-11-27 17:44                             ` Logan Gunthorpe
2017-11-27 18:57                               ` Joe Perches
2017-11-27 19:58                                 ` Logan Gunthorpe
2017-11-27 20:49                                   ` Julia Lawall
2017-11-27 22:56                                     ` Logan Gunthorpe
2017-11-28  0:15                                   ` Joe Perches
2017-11-26 16:55   ` Logan Gunthorpe
2017-11-26 17:09     ` Julia Lawall
2017-11-26 17:47       ` Logan Gunthorpe
2017-11-26 18:17         ` Julia Lawall
2017-11-26 18:33           ` Logan Gunthorpe
2017-11-27  1:35           ` Joe Perches
2017-11-27  6:40             ` Julia Lawall
2017-11-27  6:42               ` Julia Lawall
2017-11-27  6:53                 ` Logan Gunthorpe
2017-11-27  6:57                   ` Julia Lawall
2017-11-27  9:03                 ` Joe Perches

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=alpine.DEB.2.20.1711270732550.2369@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=logang@deltatee.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