linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: pxa: ssp: Fix build error by removing originally incorrect DT binding
Date: Mon, 21 Sep 2015 20:06:31 +0200	[thread overview]
Message-ID: <87bncvr6jc.fsf@belgarion.home> (raw)
In-Reply-To: <20150921151503.GK2381@localhost> (Vinod Koul's message of "Mon, 21 Sep 2015 20:45:03 +0530")

Vinod Koul <vinod.koul@intel.com> writes:

>> Now knowing if it is v4.3-rc3 is another story, as currently the pxa platform is
>> broken because of a dmaengine regression. And if the necessary fix is not
>> applied through dmaengine tree (by lack of time from Vinod), I'll want to carry
>> it through my tree, which is the reason why I have not made the pull request
>> yet.
>
> Which ones are required for fixing, I will priortize those...
Hi Vinod,

My favorite (which fixes it fully) is :
 - https://lkml.org/lkml/2015/9/6/112 (ie. only 1/3)

As a fallback plan, if the above patch is too risky for a -rc serie, my fallback
plan is :
 - https://lkml.org/lkml/2015/9/21/128

PXA can sustain only the fallback for v4.3, but the favorite has to be in v4.4,
with its 2 other brothers, in a form or another. Fallback plan is compatible
with the favorite, ie. fallback should not be reverted after favorite is applied.

Cheers.

-- 
Robert

      reply	other threads:[~2015-09-21 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07  7:23 [PATCH v2] ARM: pxa: ssp: Fix build error by removing originally incorrect DT binding Jarkko Nikula
2015-09-12 13:43 ` Robert Jarzmik
2015-09-21  7:48   ` Jarkko Nikula
2015-09-21  9:03     ` Robert Jarzmik
2015-09-21 15:15       ` Vinod Koul
2015-09-21 18:06         ` Robert Jarzmik [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=87bncvr6jc.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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).