From: Thierry Reding <thierry.reding@gmail.com>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: linux-pwm@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, rdunlap@infradead.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCHv3 0/3] ftm-pwm: Convert to direct regmap API usage
Date: Mon, 18 Aug 2014 10:31:35 +0200 [thread overview]
Message-ID: <20140818083134.GB31171@ulmo> (raw)
In-Reply-To: <1408332755-35102-1-git-send-email-Li.Xiubo@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Mon, Aug 18, 2014 at 11:32:32AM +0800, Xiubo Li wrote:
>
> This is depended on the following patches, which has been applied by
> Mark into his Regmap-Tree:
> https://lkml.org/lkml/2014/7/15/6
> https://lkml.org/lkml/2014/7/15/5
> https://lkml.org/lkml/2014/7/15/7
This doesn't seem to have any build dependencies on the above patches.
So with only this applied to the PWM tree at worst the registers will be
accessed in the wrong endianess and the PWM won't work as expected. Does
that matter? Or should I request a stable branch from Mark to pull into
the PWM tree so that this doesn't happen?
In linux-next things should be fine since both branches will be merged.
I guess there could still be an issue depending on the order in which
Linus merges the trees for 3.18, in which case there could be a brief
period where Linus' tree runtime-breaks on platforms requiring this. But
I'm not sure if that's really an issue.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-18 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 3:32 [PATCHv3 0/3] ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-08-18 3:32 ` [PATCHv3 1/3] pwm: ftm-pwm: Clean up the code Xiubo Li
2014-08-18 3:32 ` [PATCHv3 2/3] pwm: ftm-pwm: Convert to direct regmap API usage Xiubo Li
2014-08-18 8:36 ` Thierry Reding
2014-08-18 8:45 ` Li.Xiubo-KZfg59tc24xl57MIdRCFDg
2014-08-18 3:32 ` [PATCHv3 3/3] pwm: documentation: Add 'big-endian' property for FTM PWM Xiubo Li
2014-08-18 9:59 ` Mark Rutland
2014-08-18 12:11 ` Li.Xiubo
2014-08-18 8:31 ` Thierry Reding [this message]
2014-08-18 8:43 ` [PATCHv3 0/3] ftm-pwm: Convert to direct regmap API usage Li.Xiubo
2014-08-18 8:49 ` Thierry Reding
2014-08-18 8:55 ` 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=20140818083134.GB31171@ulmo \
--to=thierry.reding@gmail.com \
--cc=Li.Xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.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 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).