From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [PATCH resend 0/3] ARM: dts: sunxi: Add lradc nodes
Date: Tue, 6 Jan 2015 10:33:15 +0100 [thread overview]
Message-ID: <20150106093315.GF7853@lukather> (raw)
In-Reply-To: <1419329602-11552-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Tue, Dec 23, 2014 at 11:13:19AM +0100, Hans de Goede wrote:
> Hi Maxime, et al,
>
> Here is a resend of the sun4i-lradc dts bits, which seems to have fallen
> through the cracks. This is a resend of the last version (I don't remember
> what version we were at). The kernel bits have been queued up for merging
> by Dmitry in the mean time, so these should be ready to get queued up too,
> let me know if you want any changes.
Applied all three, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-06 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 10:13 [PATCH resend 0/3] ARM: dts: sunxi: Add lradc nodes Hans de Goede
[not found] ` <1419329602-11552-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-23 10:13 ` [PATCH resend 1/3] ARM: dts: sun4i: Add lradc node Hans de Goede
2014-12-23 10:13 ` [PATCH resend 2/3] ARM: dts: sun5i: " Hans de Goede
2014-12-23 10:13 ` [PATCH resend 3/3] ARM: dts: sun7i: " Hans de Goede
2015-01-06 9:33 ` 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=20150106093315.GF7853@lukather \
--to=maxime.ripard-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@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;
as well as URLs for NNTP newsgroup(s).