From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode
Date: Tue, 31 Oct 2017 09:52:07 +0100 [thread overview]
Message-ID: <20171031085207.fpoemk2bo5byjojy@flea> (raw)
In-Reply-To: <CACRpkdb+o_cfMnPDczF+WNNcVsPg3vTauqLZuCtv474MCM4sSQ@mail.gmail.com>
On Tue, Oct 31, 2017 at 09:46:54AM +0100, Linus Walleij wrote:
> On Wed, Oct 25, 2017 at 2:40 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
>
> > Did you have some time to look at this?
> >
> > The earlier we merge it the better, so ideally I'd really like to get
> > this into 4.15.
>
> Just overloaded as usual.
>
> Patches applied.
No worries, thanks for applying them ! :)
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171031/be8706ce/attachment.sig>
prev parent reply other threads:[~2017-10-31 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 20:53 [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode Maxime Ripard
2017-10-09 20:53 ` [PATCH v2 1/3] pinctrl: sunxi: Introduce the strict flag Maxime Ripard
2017-10-31 8:44 ` Linus Walleij
2017-10-09 20:53 ` [PATCH v2 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers Maxime Ripard
2017-10-31 8:45 ` Linus Walleij
2017-10-09 20:53 ` [PATCH v2 3/3] pinctrl: sunxi: Enforce the strict mode by default Maxime Ripard
2017-10-31 8:46 ` Linus Walleij
2017-10-10 2:36 ` [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode Chen-Yu Tsai
2017-10-25 12:40 ` Maxime Ripard
2017-10-31 8:46 ` Linus Walleij
2017-10-31 8:52 ` Maxime Ripard [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=20171031085207.fpoemk2bo5byjojy@flea \
--to=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox