From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Maxime Coquelin <maxime.coquelin@st.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Hongzhou Yang <hongzhou.yang@mediatek.com>,
Patrice CHOTARD <patrice.chotard@st.com>,
Fabian Frederick <fabf@skynet.be>,
valentin.longchamp@keymile.com
Subject: Re: [PATCH] pinctrl: mvebu: add 98dx1135-pinctrl
Date: Wed, 27 Jan 2016 14:41:21 +0100 [thread overview]
Message-ID: <56A8C901.9050508@gmail.com> (raw)
In-Reply-To: <CACRpkdbNPOCNLA+XgQ=J-z2PyTuh+2=uLBjhYoJix2cXsA_a2Q@mail.gmail.com>
On 27.01.2016 14:10, Linus Walleij wrote:
> On Fri, Dec 11, 2015 at 1:44 AM, Chris Packham
> <chris.packham@alliedtelesis.co.nz> wrote:
>> The Marvell 98DX1135 is a switch chip with an integrated CPU,
>> similar to the MV98DX4122. From a pinctrl point of view the only
>> difference is that NF_REN, NF_WEN, NF_ALE and NF_CEN lines are
>> MPP pins instead of dedicated ones.
>>
>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
>
> I guess this patch falls in your territory, please look at it if you can.
>
> If you don't have it, ask Chris to resend it.
Yes, please resend and make sure you also include
linux-arm-kernel@lists.infradead.org which is the ARM Linux
mailing list.
> I suspect the patch needs to be rebased anyway.
We'll see. Usually 98dx-something are pretty much Kirkwoods
anyway.
Sebastian
next prev parent reply other threads:[~2016-01-27 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 0:44 [PATCH] pinctrl: mvebu: add 98dx1135-pinctrl Chris Packham
2016-01-10 19:50 ` Chris Packham
2016-01-13 15:03 ` Linus Walleij
2016-01-13 20:12 ` Chris Packham
2016-01-27 13:10 ` Linus Walleij
2016-01-27 13:41 ` Sebastian Hesselbarth [this message]
2016-01-27 13:46 ` Thomas Petazzoni
2016-01-27 19:48 ` Chris Packham
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=56A8C901.9050508@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=fabf@skynet.be \
--cc=hongzhou.yang@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=patrice.chotard@st.com \
--cc=plagnioj@jcrosoft.com \
--cc=thomas.petazzoni@free-electrons.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 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.