From: Tony Lindgren <tony@atomide.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Matt Porter <mporter@ti.com>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [PATCH] ARM: dts: AM33XX: fix gpio node numbering to match hardware
Date: Mon, 10 Sep 2012 10:03:32 -0700 [thread overview]
Message-ID: <20120910170332.GX1303@atomide.com> (raw)
In-Reply-To: <504E168C.6060603@ti.com>
* Benoit Cousson <b-cousson@ti.com> [120910 09:35]:
> + Tony
>
> Hi Matt,
>
> 30 minutes too late for my pull request :-(
>
> There are a couple of am33xx patches under discussion, so I'll take them
> and send a for_3.7/dts-part2 pull request if this is not too late for Tony.
Yes please do, it' hard to say when exactly we need to stop merging,
but probably we still have a bit more time.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: AM33XX: fix gpio node numbering to match hardware
Date: Mon, 10 Sep 2012 10:03:32 -0700 [thread overview]
Message-ID: <20120910170332.GX1303@atomide.com> (raw)
In-Reply-To: <504E168C.6060603@ti.com>
* Benoit Cousson <b-cousson@ti.com> [120910 09:35]:
> + Tony
>
> Hi Matt,
>
> 30 minutes too late for my pull request :-(
>
> There are a couple of am33xx patches under discussion, so I'll take them
> and send a for_3.7/dts-part2 pull request if this is not too late for Tony.
Yes please do, it' hard to say when exactly we need to stop merging,
but probably we still have a bit more time.
Regards,
Tony
next prev parent reply other threads:[~2012-09-10 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 16:20 [PATCH] ARM: dts: AM33XX: fix gpio node numbering to match hardware Matt Porter
2012-09-10 16:20 ` Matt Porter
[not found] ` <1347294020-22661-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2012-09-10 16:34 ` Benoit Cousson
2012-09-10 16:34 ` Benoit Cousson
2012-09-10 16:34 ` Benoit Cousson
[not found] ` <504E168C.6060603-l0cyMroinI0@public.gmane.org>
2012-09-10 16:52 ` Matt Porter
2012-09-10 16:52 ` Matt Porter
2012-09-10 16:52 ` Matt Porter
2012-09-10 16:59 ` Benoit Cousson
2012-09-10 16:59 ` Benoit Cousson
2012-09-10 16:59 ` Benoit Cousson
2012-09-10 19:51 ` Matt Porter
2012-09-10 19:51 ` Matt Porter
[not found] ` <504E1C69.30602-l0cyMroinI0@public.gmane.org>
2012-09-11 5:00 ` Hiremath, Vaibhav
2012-09-11 5:00 ` Hiremath, Vaibhav
2012-09-11 5:00 ` Hiremath, Vaibhav
2012-09-10 17:03 ` Tony Lindgren [this message]
2012-09-10 17:03 ` Tony Lindgren
2012-09-11 4:57 ` Hiremath, Vaibhav
2012-09-11 4:57 ` Hiremath, Vaibhav
2012-09-11 4:57 ` Hiremath, Vaibhav
2012-09-11 11:29 ` Matt Porter
2012-09-11 11:29 ` Matt Porter
2012-09-11 11:30 ` Hiremath, Vaibhav
2012-09-11 11:30 ` Hiremath, Vaibhav
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=20120910170332.GX1303@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.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.