From: Ralf Baechle <ralf@linux-mips.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Florian Fainelli <florian@openwrt.org>,
Maxime Bizon <mbizon@freebox.fr>,
linux-mips <linux-mips@linux-mips.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: includecheck fix: bcm63xx, board_bcm963xx.c
Date: Wed, 23 Sep 2009 10:11:21 +0100 [thread overview]
Message-ID: <20090923091121.GA5457@linux-mips.org> (raw)
In-Reply-To: <1253626037.3784.13.camel@ht.satnam>
On Tue, Sep 22, 2009 at 06:57:17PM +0530, Jaswinder Singh Rajput wrote:
> fix the following 'make includecheck' warning:
>
> arch/mips/bcm63xx/boards/board_bcm963xx.c: bcm63xx_board.h is included more than once.
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
I've already merged a patch which didn't yet make it to kernel.org for this
issue a few days ago.
Thanks anyway!
Ralf
prev parent reply other threads:[~2009-09-23 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 13:27 [PATCH] MIPS: includecheck fix: bcm63xx, board_bcm963xx.c Jaswinder Singh Rajput
2009-09-23 9:11 ` Ralf Baechle [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=20090923091121.GA5457@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=florian@openwrt.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mbizon@freebox.fr \
/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;
as well as URLs for NNTP newsgroup(s).