From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Date: Wed, 15 Oct 2014 16:49:49 +0200 [thread overview]
Message-ID: <543E898D.10606@gmail.com> (raw)
In-Reply-To: <20141015144259.GB17447@titan.lakedaemon.net>
On 10/15/2014 04:42 PM, Jason Cooper wrote:
> On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote:
>> Le 6 oct. 2014 ? 18:13, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> a ?crit :
>>> I prepared more branches with the series
>>> - on top of v3.17 release:
>>> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
>>>
>>> - on top of next-20141003 (i.e. what will become v3.18-rc1):
>>> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
>>>
>>> It would be great, if you can test in this order:
>>> - vanilla v3.17
>>> - mvebu-ix4_v3.17
>>> - mvebu-ix4_next-20141003
>>>
>> All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig
>>
>> The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :(
>>
>> This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged.
>
> Do you have a link to an email thread or the patch Subject line? I can
> confirm it's missing from mvebu/fixes...
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html
But you and Andrew should check what Arnd suggested. IIRC, there
was also an appropriate follow-up patch discussion started by
Andrew.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>,
Benoit Masson <benoitm@perenite.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Benoit Masson <yahoo@perenite.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes
Date: Wed, 15 Oct 2014 16:49:49 +0200 [thread overview]
Message-ID: <543E898D.10606@gmail.com> (raw)
In-Reply-To: <20141015144259.GB17447@titan.lakedaemon.net>
On 10/15/2014 04:42 PM, Jason Cooper wrote:
> On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote:
>> Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> a écrit :
>>> I prepared more branches with the series
>>> - on top of v3.17 release:
>>> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
>>>
>>> - on top of next-20141003 (i.e. what will become v3.18-rc1):
>>> https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
>>>
>>> It would be great, if you can test in this order:
>>> - vanilla v3.17
>>> - mvebu-ix4_v3.17
>>> - mvebu-ix4_next-20141003
>>>
>> All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig
>>
>> The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :(
>>
>> This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged.
>
> Do you have a link to an email thread or the patch Subject line? I can
> confirm it's missing from mvebu/fixes...
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html
But you and Andrew should check what Arnd suggested. IIRC, there
was also an appropriate follow-up patch discussion started by
Andrew.
Sebastian
next prev parent reply other threads:[~2014-10-15 14:49 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 20:14 [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 1/8] ARM: mvebu: armada-xp: Consolidate pinctrl node Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:39 ` Thomas Petazzoni
2014-09-19 20:39 ` Thomas Petazzoni
2014-09-19 20:39 ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 2/8] ARM: mvebu: armada-xp: Add node alias to pinctrl and add base address Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:40 ` Thomas Petazzoni
2014-09-19 20:40 ` Thomas Petazzoni
2014-09-19 20:40 ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 3/8] ARM: mvebu: armada-xp: Use pinctrl node alias Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:42 ` Thomas Petazzoni
2014-09-19 20:42 ` Thomas Petazzoni
2014-09-19 20:14 ` [PATCH 4/8] ARM: mvebu: armada-xp: Move GE0/1 pinctrl settings for RGMII Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 5/8] ARM: mvebu: armada-xp: Add GE0 pinctrl settings for GMII Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 6/8] ARM: mvebu: armada-xp: Add RGMII pinctrl to Lenovo ix4-300d Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 7/8] ARM: mvebu: armada-xp: Add I2C eeprom on " Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-20 9:55 ` Sebastian Hesselbarth
2014-09-20 9:55 ` Sebastian Hesselbarth
2014-09-20 9:55 ` Sebastian Hesselbarth
2014-09-19 20:14 ` [PATCH 8/8] ARM: mvebu: armada-xp: Fix 74hc595 count for " Sebastian Hesselbarth
2014-09-19 20:14 ` Sebastian Hesselbarth
2014-09-21 14:11 ` [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes Benoit Masson
2014-09-21 14:11 ` Benoit Masson
2014-10-03 14:11 ` Jason Cooper
2014-10-03 14:11 ` Jason Cooper
2014-10-03 14:11 ` Jason Cooper
2014-10-03 15:06 ` Sebastian Hesselbarth
2014-10-03 15:06 ` Sebastian Hesselbarth
2014-10-03 15:06 ` Sebastian Hesselbarth
2014-10-03 15:29 ` Benoit Masson
2014-10-03 15:29 ` Benoit Masson
2014-10-03 15:41 ` Sebastian Hesselbarth
2014-10-03 15:41 ` Sebastian Hesselbarth
2014-10-05 23:11 ` Benoit Masson
2014-10-05 23:11 ` Benoit Masson
2014-10-06 7:47 ` Sebastian Hesselbarth
2014-10-06 7:47 ` Sebastian Hesselbarth
2014-10-06 7:47 ` Sebastian Hesselbarth
2014-10-06 8:36 ` Gregory CLEMENT
2014-10-06 8:36 ` Gregory CLEMENT
2014-10-06 8:36 ` Gregory CLEMENT
[not found] ` <BAB12F2D-0142-4362-BA04-59D8E6B16AAE@perenite.com>
2014-10-06 9:14 ` Gregory CLEMENT
2014-10-06 9:14 ` Gregory CLEMENT
2014-10-06 9:14 ` Gregory CLEMENT
2014-10-06 16:13 ` Sebastian Hesselbarth
2014-10-06 16:13 ` Sebastian Hesselbarth
2014-10-15 0:53 ` Benoit Masson
2014-10-15 0:53 ` Benoit Masson
2014-10-15 0:53 ` Benoit Masson
[not found] ` <1CDF8F6B-42FF-4D6A-B52F-6DB270F2673C@perenite.com>
2014-10-15 14:41 ` Andrew Lunn
2014-10-15 14:41 ` Andrew Lunn
2014-10-15 15:35 ` Benoit Masson
2014-10-15 15:35 ` Benoit Masson
2014-10-15 14:42 ` Jason Cooper
2014-10-15 14:42 ` Jason Cooper
2014-10-15 14:49 ` Sebastian Hesselbarth [this message]
2014-10-15 14:49 ` Sebastian Hesselbarth
2014-10-15 14:55 ` Andrew Lunn
2014-10-15 14:55 ` Andrew Lunn
2014-10-15 14:55 ` Andrew Lunn
2014-10-15 15:30 ` Jason Cooper
2014-10-15 15:30 ` Jason Cooper
2014-10-15 15:56 ` Jason Cooper
2014-10-15 15:56 ` Jason Cooper
2014-11-01 22:59 ` Jason Cooper
2014-11-01 22:59 ` Jason Cooper
2014-11-01 22:36 ` Jason Cooper
2014-11-01 22:36 ` Jason Cooper
2014-11-01 22:36 ` Jason Cooper
2014-11-01 22:48 ` Sebastian Hesselbarth
2014-11-01 22:48 ` Sebastian Hesselbarth
2014-11-01 22:48 ` Sebastian Hesselbarth
2014-11-02 19:03 ` Jason Cooper
2014-11-02 19:03 ` Jason Cooper
2014-11-02 19:03 ` Jason Cooper
2014-11-02 19:19 ` Sebastian Hesselbarth
2014-11-02 19:19 ` Sebastian Hesselbarth
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=543E898D.10606@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.