From: Wolfram Sang <wsa@the-dreams.de>
To: Danielle Costantino <danielle.costantino@gmail.com>
Cc: Valentin Longchamp <valentin.longchamp@keymile.com>,
Linux device trees <devicetree@vger.kernel.org>,
"Boschung, Rainer" <Rainer.Boschung@keymile.com>,
"Brunck, Holger" <Holger.Brunck@keymile.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
Scott Wood <scottwood@freescale.com>,
Linux PowerPC Kernel <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] i2c-qoriq: modified compatibility for correct prescaler
Date: Mon, 1 Dec 2014 18:23:20 +0100 [thread overview]
Message-ID: <20141201172320.GC3212@katana> (raw)
In-Reply-To: <CAAVjN7fJyOh64p5UGRmv-UTnF47cERDfbHyHTuzQmQj8xTDEOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
> I saw that this patch was marked as not applicable, but on most qoriq
> devices the pre-scaler is 2 especially for p2020/p2010 devices
> arch/powerpc/boot/dts/fsl/p2020si-post.dtsi
Just for completeness: "Not applicable" given from patchwork of the i2c
subsystem means this patch is not for the i2c subsystem. In this case,
it is for powerpc because it was modifying powerpc dts files only. That
doesn't say anything about the patch itself.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-01 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 9:27 [PATCH] i2c-qoriq: modified compatibility for correct prescaler Valentin Longchamp
2014-10-28 23:08 ` Scott Wood
2014-10-29 8:59 ` Valentin Longchamp
2014-11-06 21:58 ` Scott Wood
2014-11-13 0:34 ` Wolfram Sang
2014-11-14 7:43 ` Valentin Longchamp
2014-11-14 8:28 ` Wolfram Sang
2014-11-18 1:28 ` Scott Wood
2014-11-25 18:13 ` Wolfram Sang
2014-11-26 1:41 ` Scott Wood
2014-11-30 4:30 ` Danielle Costantino
2014-12-01 17:23 ` Wolfram Sang [this message]
2014-12-11 13:44 ` Valentin Longchamp
2014-12-23 13:23 ` Valentin Longchamp
2014-12-23 13:49 ` Wolfram Sang
2014-12-27 2:43 ` Scott Wood
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=20141201172320.GC3212@katana \
--to=wsa@the-dreams.de \
--cc=Holger.Brunck@keymile.com \
--cc=Rainer.Boschung@keymile.com \
--cc=danielle.costantino@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=valentin.longchamp@keymile.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).