From: Mark Brown <broonie@kernel.org>
To: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
"wim@iguana.be" <wim@iguana.be>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"swarren@nvidia.com" <swarren@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 2/2] watchdog: imx2_wdt: Add big-endian support
Date: Tue, 1 Apr 2014 13:24:54 +0100 [thread overview]
Message-ID: <20140401122454.GS2269@sirena.org.uk> (raw)
In-Reply-To: <1c79a81bbd7b4cc79689cb907e81e893@BY2PR03MB505.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
On Tue, Apr 01, 2014 at 02:24:12AM +0000, Li.Xiubo@freescale.com wrote:
> Yes, I do think so too and there has already regmap-mmio version patch
> Series about the IMX2 Watchdog driver, but those regmap patches for
> supporting the 16-bit values are in Mark's tree and the IMX2 Watchdog
> will depend on them.
> How to deal with this situation ?
Well, anything that's already applied went to Linus already so is in
-rc1. Anything else we can either do a cross tree merge or I can apply
the driver.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-01 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 2:21 [PATCHv2 0/2] Add big endian support Xiubo Li
2014-03-26 2:21 ` [PATCHv2 1/2] watchdog: imx2_wdt: Sort the header files alphabetically Xiubo Li
2014-03-26 2:21 ` [PATCHv2 2/2] watchdog: imx2_wdt: Add big-endian support Xiubo Li
2014-03-31 3:32 ` Guenter Roeck
2014-03-31 4:18 ` Li.Xiubo
2014-04-01 1:45 ` Guenter Roeck
2014-04-01 2:24 ` Li.Xiubo
2014-04-01 12:24 ` Mark Brown [this message]
2014-04-02 7:33 ` Li.Xiubo
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=20140401122454.GS2269@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Li.Xiubo@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=swarren@nvidia.com \
--cc=w.sang@pengutronix.de \
--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