From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Dirk Behme <dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
Cc: Hui Wang <jason77.wang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
"Wohlrab Knut \(CM-AI/PJ-CF31\)"
<Knut.Wohlrab-V5te9oGctAVWk0Htik3J/w@public.gmane.org>,
"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH] spi/imx: set the inactive state of the clock according to the clock polarity
Date: Tue, 25 Sep 2012 07:08:32 -0400 [thread overview]
Message-ID: <20120925110831.GB4428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5060448A.9060506-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
On Mon, Sep 24, 2012 at 01:31:22PM +0200, Dirk Behme wrote:
> Let me know if you can find above thread on one of the both mailing
> lists. If not, I would be happy to resend it again.
Yes, of course - it's hard to apply patches from web archives.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
prev parent reply other threads:[~2012-09-25 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 8:55 [PATCH] spi/imx: set the inactive state of the clock according to the clock polarity Dirk Behme
[not found] ` <1346403311-25080-1-git-send-email-dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2012-08-31 2:35 ` Shawn Guo
2012-09-21 7:36 ` Dirk Behme
[not found] ` <505C1913.1090004-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2012-09-21 7:54 ` Uwe Kleine-König
[not found] ` <20120921075431.GS5525-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-09-22 6:10 ` Dirk Behme
[not found] ` <505D5668.4040209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-22 13:44 ` Fabio Estevam
2012-09-24 5:06 ` Shawn Guo
[not found] ` <20120924050655.GA27291-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-09-24 6:34 ` Dirk Behme
[not found] ` <505FFEF3.3000605-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2012-09-24 10:02 ` Mark Brown
[not found] ` <20120924100226.GA21375-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-09-24 11:31 ` Dirk Behme
[not found] ` <5060448A.9060506-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2012-09-25 11:08 ` Mark Brown [this message]
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=20120925110831.GB4428@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=Knut.Wohlrab-V5te9oGctAVWk0Htik3J/w@public.gmane.org \
--cc=dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org \
--cc=jason77.wang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).