From: "Keiji Hayashibara" <hayashibara.keiji@socionext.com>
To: "Yamada, Masahiro/山田 真弘" <yamada.masahiro@socionext.com>
Cc: wim@iguana.be, "Guenter Roeck" <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
"Masami Hiramatsu" <masami.hiramatsu@linaro.org>,
"Jassi Brar" <jaswinder.singh@linaro.org>,
"Hayashi, Kunihiko/林 邦彦" <hayashi.kunihiko@socionext.com>,
"Owada, Kiyoshi/大和田 清志" <owada.kiyoshi@socionext.com>
Subject: RE: [PATCH V2 2/3] watchdog: uniphier: add UniPhier watchdog driver
Date: Thu, 8 Jun 2017 14:51:21 +0900 [thread overview]
Message-ID: <000001d2e01b$41b00840$c51018c0$@socionext.com> (raw)
In-Reply-To: <CAK7LNARQb3r7fvytCZ86G3iQBpWhu7-06DY9gcJswjH0heUonA@mail.gmail.com>
Hello Yamada-san,
> > +
> > +#include <linux/module.h>
> > +#include <linux/mfd/syscon.h>
> > +#include <linux/of.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/regmap.h>
> > +#include <linux/watchdog.h>
> > +#include <linux/bitops.h>
>
> I think you should have added <linux/bitops.h> on the top
> to keep the includes alphabetically sorted.
Sorry, I will fix in v3 patch.
----------
Best Regards,
Keiji Hayashibara
next prev parent reply other threads:[~2017-06-08 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 9:11 [PATCH V2 0/3] add UniPhier watchdog support Keiji Hayashibara
2017-06-06 9:11 ` [PATCH V2 1/3] devicetree: add UniPhier WDT devicetree bindings documentation Keiji Hayashibara
2017-06-08 2:11 ` Masahiro Yamada
2017-06-08 6:22 ` Keiji Hayashibara
2017-06-06 9:11 ` [PATCH V2 2/3] watchdog: uniphier: add UniPhier watchdog driver Keiji Hayashibara
2017-06-08 2:09 ` Masahiro Yamada
2017-06-08 5:51 ` Keiji Hayashibara [this message]
2017-06-08 12:31 ` Guenter Roeck
2017-06-09 10:22 ` Keiji Hayashibara
2017-06-06 9:11 ` [PATCH V2 3/3] arm64: dts: uniphier: add watchdog node for LD11 and LD20 Keiji Hayashibara
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='000001d2e01b$41b00840$c51018c0$@socionext.com' \
--to=hayashibara.keiji@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masami.hiramatsu@linaro.org \
--cc=owada.kiyoshi@socionext.com \
--cc=robh+dt@kernel.org \
--cc=wim@iguana.be \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).