public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: alexander.levin@verizon.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] tools/lib/lockdep: Add missing declaration of 'pr_cont()'
Date: Fri, 8 Dec 2017 07:19:13 +0100	[thread overview]
Message-ID: <20171208061913.4pvol2tezybgbdzr@gmail.com> (raw)
In-Reply-To: <20171207161057.7406-2-alexander.levin@verizon.com>


* alexander.levin@verizon.com <alexander.levin@verizon.com> wrote:

> From: Mengting Zhang <zhangmengting@huawei.com>
> 
> An annoying compile warning due to missing declaration is shown below:
> In file included from lockdep.c:27:0:
> ../../../kernel/locking/lockdep.c: In function 'print_unlock_imbalance_bug' :
> ../../../kernel/locking/lockdep.c:3544:2: warning: implicit declaration of function 'pr_cont' [-Wimplicit-function-declaration]
>   pr_cont(") at:\n");
>   ^

All build warnings are annoying, please formulate this in a more neutral fashion.

Also, please separate the compiler splat from the changelog text with an empty 
line, and align it vertically as well so that it seprates more.

Please do this for the second patch as well, and try to harmonize the style of the 
changelogs.

This is an example of a clean changelog that fixes a build warning:

commit 1b3b5219abfd6a214e99018747e9fe98514b43ca
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Nov 27 12:18:23 2017 -0300

    tools headers: Syncronize mman.h ABI header
    
    To add support for the MAP_SYNC flag introduced in:
    
      b6fb293f2497 ("mm: Define MAP_SYNC and VM_SYNC flags")
    
    Update tools/perf/trace/beauty/mmap.c to support that flag.
    
    This silences this perf build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/asm-generic/mman.h' differs from latest version at 'include/uapi/asm-generic/mman.h'
    
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: David Ahern <dsahern@gmail.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Wang Nan <wangnan0@huawei.com>
    Link: https://lkml.kernel.org/n/tip-14zyk3iywrj37c7g1eagmzbo@git.kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

Thanks,

	Ingo

  reply	other threads:[~2017-12-08  6:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 16:11 [PATCH 0/2] tools/lib/lockdep: fixes for v4.15 alexander.levin
2017-12-07 16:11 ` [PATCH 2/2] tools/lib/lockdep: add empty declaration for early_param alexander.levin
2017-12-08  6:09   ` Ingo Molnar
2017-12-08  6:20     ` Ingo Molnar
2017-12-08 14:03       ` alexander.levin
2017-12-11 14:45         ` Ingo Molnar
2017-12-07 16:11 ` [PATCH 1/2] tools/lib/lockdep: Add missing declaration of 'pr_cont()' alexander.levin
2017-12-08  6:19   ` Ingo Molnar [this message]
2017-12-08  6:07 ` [PATCH 0/2] tools/lib/lockdep: fixes for v4.15 Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-12-12 18:16 [GIT PULL " alexander.levin
2017-12-12 18:16 ` [PATCH 1/2] tools/lib/lockdep: Add missing declaration of 'pr_cont()' alexander.levin

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=20171208061913.4pvol2tezybgbdzr@gmail.com \
    --to=mingo@kernel.org \
    --cc=alexander.levin@verizon.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox