From: Joe Perches <joe@perches.com>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
linux-mips@linux-mips.org
Cc: Aleksandar Markovic <aleksandar.markovic@mips.com>,
"David S. Miller" <davem@davemloft.net>,
Douglas Leung <douglas.leung@mips.com>,
Goran Ferenc <goran.ferenc@mips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Hogan <james.hogan@mips.com>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Miodrag Dinic <miodrag.dinic@mips.com>,
Paul Burton <paul.burton@mips.com>,
Petar Jovanovic <petar.jovanovic@mips.com>,
Raghu Gandham <raghu.gandham@mips.com>,
Ralf Baechle <ralf@linux-mips.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v11 0/3] MIPS: Add virtual Ranchu board as a generic-based board
Date: Fri, 15 Dec 2017 09:12:24 -0800 [thread overview]
Message-ID: <1513357944.4647.1.camel@perches.com> (raw)
In-Reply-To: <1513356553-7238-1-git-send-email-aleksandar.markovic@rt-rk.com>
On Fri, 2017-12-15 at 17:48 +0100, Aleksandar Markovic wrote:
> Checkpatch script outputs a small number of warnings if applied to
> this series. We did not correct the code, since we think the code is
> correct for those particular cases of checkpatch warnings.
What are those warnings? I don't see any.
next prev parent reply other threads:[~2017-12-15 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 16:48 [PATCH v11 0/3] MIPS: Add virtual Ranchu board as a generic-based board Aleksandar Markovic
2017-12-15 16:48 ` [PATCH v11 1/3] Documentation: Add device tree binding for Goldfish PIC driver Aleksandar Markovic
2017-12-15 16:48 ` Aleksandar Markovic
2017-12-15 16:48 ` [PATCH v11 2/3] irqchip/irq-goldfish-pic: Add " Aleksandar Markovic
2017-12-15 16:48 ` [PATCH v11 3/3] MIPS: ranchu: Add Ranchu as a new generic-based board Aleksandar Markovic
2017-12-15 17:12 ` Joe Perches [this message]
2017-12-15 17:55 ` [PATCH v11 0/3] MIPS: Add virtual Ranchu board as a " Aleksandar Markovic
2017-12-25 15:23 ` Aleksandar Markovic
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=1513357944.4647.1.camel@perches.com \
--to=joe@perches.com \
--cc=aleksandar.markovic@mips.com \
--cc=aleksandar.markovic@rt-rk.com \
--cc=davem@davemloft.net \
--cc=douglas.leung@mips.com \
--cc=goran.ferenc@mips.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.hogan@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mchehab@kernel.org \
--cc=miodrag.dinic@mips.com \
--cc=paul.burton@mips.com \
--cc=petar.jovanovic@mips.com \
--cc=raghu.gandham@mips.com \
--cc=ralf@linux-mips.org \
--cc=rdunlap@infradead.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 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.