All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: YueHaibing <yuehaibing@huawei.com>
Cc: ralf@linux-mips.org, paulburton@kernel.org, tglx@linutronix.de,
	sboyd@kernel.org, geert+renesas@glider.be, f4bug@amsat.org,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] MIPS: pic32mzda: Drop pointless static qualifier
Date: Fri, 28 Feb 2020 12:45:44 +0100	[thread overview]
Message-ID: <20200228114544.GA10905@alpha.franken.de> (raw)
In-Reply-To: <20200227070502.106762-1-yuehaibing@huawei.com>

On Thu, Feb 27, 2020 at 07:05:02AM +0000, YueHaibing wrote:
> There is no need to have the 'struct device_node *node' variable static
> since new value always be assigned before use it.
> 
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
>  arch/mips/pic32/pic32mzda/time.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: YueHaibing <yuehaibing@huawei.com>
Cc: ralf@linux-mips.org, paulburton@kernel.org, tglx@linutronix.de,
	sboyd@kernel.org, geert+renesas@glider.be, f4bug@amsat.org,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] MIPS: pic32mzda: Drop pointless static qualifier
Date: Fri, 28 Feb 2020 11:45:44 +0000	[thread overview]
Message-ID: <20200228114544.GA10905@alpha.franken.de> (raw)
In-Reply-To: <20200227070502.106762-1-yuehaibing@huawei.com>

On Thu, Feb 27, 2020 at 07:05:02AM +0000, YueHaibing wrote:
> There is no need to have the 'struct device_node *node' variable static
> since new value always be assigned before use it.
> 
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
>  arch/mips/pic32/pic32mzda/time.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2020-02-28 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  7:05 [PATCH -next] MIPS: pic32mzda: Drop pointless static qualifier YueHaibing
2020-02-27  7:05 ` YueHaibing
2020-02-28 11:45 ` Thomas Bogendoerfer [this message]
2020-02-28 11:45   ` Thomas Bogendoerfer

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=20200228114544.GA10905@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=f4bug@amsat.org \
    --cc=geert+renesas@glider.be \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yuehaibing@huawei.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.