[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOS58YM_1MbngkEvoVtLpJqj3z-fpiQNyog0YK9fdSD7epYYcQ@mail.gmail.com>
Date: Fri, 9 Aug 2013 12:15:45 -0400
From: Tejun Heo <tj@...nel.org>
To: Mark Langsdorf <mark.langsdorf@...xeda.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"pawel.moll@....com" <pawel.moll@....com>,
"mark.rutland@....com" <mark.rutland@....com>,
"swarren@...dotorg.org" <swarren@...dotorg.org>,
"ian.campbell@...rix.com" <ian.campbell@...rix.com>,
Rob Herring <rob.herring@...xeda.com>,
"sergei.shtylyov@...entembedded.com"
<sergei.shtylyov@...entembedded.com>
Subject: Re: [PATCH v3 3/5] devicetree: create a separate binding description
for sata_highbank
Hello, Mark.
On Fri, Aug 9, 2013 at 12:12 PM, Mark Langsdorf
<mark.langsdorf@...xeda.com> wrote:
> I'll update the description when I resubmit it to give you more detail on
> the impact.
Yes, please give me some hints on to which branch the patches are
targeted and whether stable should be cc'd. I can't really tell just
looking at the patches as I have no idea how widespread the device is
in the wild and which kernels they'd be running or how critical being
out-of-spec is (is it gonna burn phys on the receiving end in the long
term? or is it just noisier and the link is gonna be more susceptible
to errors from EM interferences and so on) and how risky the fixes
are.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists