From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: socfpga-next
Date: Thu, 3 Oct 2013 08:31:58 -0500 [thread overview]
Message-ID: <1380807118.30559.3.camel@linux-builds1> (raw)
In-Reply-To: <20131003130240.GS9632@pengutronix.de>
Hi Robert,
On Thu, 2013-10-03 at 15:02 +0200, Robert Schwebel wrote:
> Hi Dinh,
>
> On Wed, Oct 02, 2013 at 09:35:29AM +0200, Steffen Trumtrar wrote:
> > BTW: It seems there is no official maintainer(tree) for the socfpga dt stuff.
> > So, I rebased onto next-20130927.
>
> It would be great if you could establish some kind of socfpga-next tree,
> where we can see what you have already taken, and which could be put
> into linux-next.
>
> What do you think?
Do you mean at kernel.org or just at any other place? I have a git repo
that I'm managing with commits that are sent out for review or have
Acks.
git://git.rocketboards.org/linux-socfpga-next.git
next-dt : DTS updates
for-next : latest from Linus + patches(being reviewed)
Dinh
>
> rsc
next prev parent reply other threads:[~2013-10-03 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 13:02 socfpga-next Robert Schwebel
2013-10-03 13:31 ` Dinh Nguyen [this message]
2013-10-03 14:10 ` socfpga-next Steffen Trumtrar
2013-10-03 14:34 ` socfpga-next Dinh Nguyen
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=1380807118.30559.3.camel@linux-builds1 \
--to=dinguyen@altera.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 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.