From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Henry Paulissen <henry-oxlTVf6CAJF4HdFT58BDcQ@public.gmane.org>
Cc: linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
draakje197-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
wens-jdAy2FN1RRM@public.gmane.org,
andre.przywara-5wv7dgnIgG8@public.gmane.org,
plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org,
maxime.coquelin-qxv4g6HH51o@public.gmane.org,
lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
hongzhou.yang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 699 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
next prev parent reply other threads:[~2016-02-25 17:42 UTC|newest]
Thread overview: 6+ 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
[not found] ` <1456161251-2303-1-git-send-email-henry-oxlTVf6CAJF4HdFT58BDcQ@public.gmane.org>
2016-02-25 0:54 ` Maxime Ripard
2016-02-25 14:16 ` Linus Walleij
[not found] ` <CACRpkdYmf8-ZPV5q9H3cdZtQDUkbx=bcrVg9a8M3zEAifXxF9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-25 14:26 ` Henry Paulissen
[not found] ` <280e414e-546e-4a91-91a6-a4fa7157db49-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
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-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=andre.przywara-5wv7dgnIgG8@public.gmane.org \
--cc=draakje197-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org \
--cc=henry-oxlTVf6CAJF4HdFT58BDcQ@public.gmane.org \
--cc=hongzhou.yang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.coquelin-qxv4g6HH51o@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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