From: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "wim@iguana.be" <wim@iguana.be>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCHv4 2/2] watchdog: imx2_wdt: convert to use regmap API.
Date: Fri, 4 Apr 2014 02:09:14 +0000 [thread overview]
Message-ID: <45be66f717074e4b85c5fc531e05045f@BY2PR03MB505.namprd03.prod.outlook.com> (raw)
In-Reply-To: <533E0FB3.6070305@roeck-us.net>
> > This is caused by not compiling the regmap core.
> >
> > Could you add the following patch to have a try ?
> > ==========================
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index 79d2589..3e55fa9 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -369,6 +369,7 @@ config MAX63XX_WATCHDOG
> > config IMX2_WDT
> > tristate "IMX2+ Watchdog"
> > depends on ARCH_MXC
> > + select REGMAP_MMIO
> > help
> > This is the driver for the hardware watchdog
> > on the Freescale IMX2 and later processors.
> > --------------------------
> >
> > If it's okey, I'll sent the v5 series to fix this.
> >
> Yes, that fixes the problem.
>
I'll send the v5 series to fix this.
Thanks very much.
next prev parent reply other threads:[~2014-04-04 2:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 1:04 [PATCHv4 0/2] imx2-wdt: Add regmap-mmio support Xiubo Li
2014-04-03 1:04 ` [PATCHv4 1/2] watchdog: imx2_wdt: Sort the header files alphabetically Xiubo Li
2014-04-03 1:04 ` [PATCHv4 2/2] watchdog: imx2_wdt: convert to use regmap API Xiubo Li
2014-04-03 16:36 ` Guenter Roeck
2014-04-04 1:13 ` Li.Xiubo
2014-04-04 1:49 ` Guenter Roeck
2014-04-04 2:09 ` Li.Xiubo [this message]
2014-04-03 2:52 ` [PATCHv4 0/2] imx2-wdt: Add regmap-mmio support Shawn Guo
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=45be66f717074e4b85c5fc531e05045f@BY2PR03MB505.namprd03.prod.outlook.com \
--to=li.xiubo@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=shawn.guo@linaro.org \
--cc=wim@iguana.be \
/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®