From: dinh.linux@gmail.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SOCFPGA DTS updates for 3.16, take 2
Date: Thu, 22 May 2014 09:26:24 -0500 [thread overview]
Message-ID: <537E0910.8010001@gmail.com> (raw)
In-Reply-To: <20140522051522.GB32618@quad.lixom.net>
On 5/22/14 12:15 AM, Olof Johansson wrote:
> On Sun, May 18, 2014 at 10:47:21PM -0500, dinguyen at altera.com wrote:
>> Hi Arnd, Kevin and Olof,
>>
>> Please consider pulling in this patch for 3.16. This patch adds the DTS
>> entries for the GPIOs on the SOCFPGA platform.
>>
>> Olof had a question regarding how the GPIO node needed 2-layer approach.
>>
>> http://thread.gmane.org/gmane.linux.kernel/1671569/focus=1702208
>>
>> I hope that Alan Tull was able to answer Olof's question.
>>
>> Thanks,
>>
>> The following changes since commit 2bfac3a551978c4953f659e1bd18d58c3c249f64:
>>
>> Merge tag 'socfpga-dt-updates-for-3.16_v3' of git://git.rocketboards.org/linux-socfpga-next into next/dt (2014-05-16 16:07:37 -0700)
> You can't base your branch on top of our next/dt. You should have based
> this on top of your previous branch, and not pulled down our contents
> for it.
Ah thanks, and sorry about that. So should my pull request start from
v3.15-rc1(was the
last rc in my branch) or the last commit that you pulled in?
>
> Please send a new pull request, or let me know if you prefer me to just
> cherry-pick over the one patch -- your choice.
Let me send you a new pull request as there is another that just came in.
Thanks,
Dinh
>
> -Olof
next prev parent reply other threads:[~2014-05-22 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 3:47 [GIT PULL] SOCFPGA DTS updates for 3.16, take 2 dinguyen at altera.com
2014-05-22 5:15 ` Olof Johansson
2014-05-22 14:26 ` Dinh Nguyen [this message]
2014-05-26 18:20 ` Olof Johansson
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=537E0910.8010001@gmail.com \
--to=dinh.linux@gmail.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;
as well as URLs for NNTP newsgroup(s).