mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wan Jiabing <wanjiabing@vivo.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	linux-kernel@vger.kernel.org, keal_w@yeah.net
Subject: Re: [PATCH] [v2] include: linux: debug_locks: Remove duplicate declaration
Date: Thu, 25 Mar 2021 17:45:22 +0200	[thread overview]
Message-ID: <YFywEil0TwbHItSJ@smile.fi.intel.com> (raw)
In-Reply-To: <20210325152029.4976-1-wanjiabing@vivo.com>

On Thu, Mar 25, 2021 at 11:20:28PM +0800, Wan Jiabing wrote:
> struct task_struct has been declared.

"...declared twice."

In the subject line the "include: linux: " part is not needed.

FWIW, after addressing above,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Remove the duplicate.
> 
> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
> ---
> Changelog:
> v2:
> - Remove another duplicate declaration for being closer
>   to its user.
> ---
>  include/linux/debug_locks.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/include/linux/debug_locks.h b/include/linux/debug_locks.h
> index 2915f56ad421..32f6a37a3d3f 100644
> --- a/include/linux/debug_locks.h
> +++ b/include/linux/debug_locks.h
> @@ -6,8 +6,6 @@
>  #include <linux/bug.h>
>  #include <linux/printk.h>
>  
> -struct task_struct;
> -
>  extern int debug_locks __read_mostly;
>  extern int debug_locks_silent __read_mostly;
>  
> -- 
> 2.25.1
> 

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2021-03-25 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 15:20 Wan Jiabing
2021-03-25 15:45 ` Andy Shevchenko [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=YFywEil0TwbHItSJ@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=keal_w@yeah.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=wanjiabing@vivo.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

all inboxes | Powered by JetHome®