All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: socfpga-next
Date: Thu, 3 Oct 2013 15:02:40 +0200	[thread overview]
Message-ID: <20131003130240.GS9632@pengutronix.de> (raw)

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?

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

             reply	other threads:[~2013-10-03 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 13:02 Robert Schwebel [this message]
2013-10-03 13:31 ` socfpga-next Dinh Nguyen
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=20131003130240.GS9632@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --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.