From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Henry Paulissen <henry@nitronetworks.nl>
Cc: linux-sunxi <linux-sunxi@googlegroups.com>,
draakje197@gmail.com, wens@csie.org, andre.przywara@arm.com,
plagnioj@jcrosoft.com, maxime.coquelin@st.com, lee@kernel.org,
hongzhou.yang@mediatek.com, fabf@skynet.be,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org
Subject: Re: [PATCH v6] Fix sun7i pin assignment for IRQ's
Date: Thu, 25 Feb 2016 09:42:02 -0800 [thread overview]
Message-ID: <20160225174202.GA31136@lukather> (raw)
In-Reply-To: <280e414e-546e-4a91-91a6-a4fa7157db49@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hi,
On Thu, Feb 25, 2016 at 06:26:22AM -0800, Henry Paulissen wrote:
>
>
> Op donderdag 25 februari 2016 15:16:49 UTC+1 schreef Linus Walleij:
>
> >
> > I'm taking this patch out of my tree now following Maxime's comments.
> >
> > I'm a bit annoyed that it is iterating too quickly as well, I will
> > wait and see for a while.
> >
> >
> All of Maxime his questions where already answered in a reply to him at:
> Date: Sun, 21 Feb 2016 11:27:46 -0800 (PST)
And I was not among the recipients of that mail, please try to keep
everyone in Cc.
Commenting on it right now....
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-25 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:14 [PATCH v6] Fix sun7i pin assignment for IRQ's Henry Paulissen
2016-02-25 0:54 ` Maxime Ripard
2016-02-25 14:16 ` Linus Walleij
[not found] ` <280e414e-546e-4a91-91a6-a4fa7157db49@googlegroups.com>
2016-02-25 17:42 ` Maxime Ripard [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 17:07 Henry Paulissen
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=20160225174202.GA31136@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=andre.przywara@arm.com \
--cc=draakje197@gmail.com \
--cc=fabf@skynet.be \
--cc=henry@nitronetworks.nl \
--cc=hongzhou.yang@mediatek.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.coquelin@st.com \
--cc=plagnioj@jcrosoft.com \
--cc=wens@csie.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