From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Remove orphaned i.MX27 DT template
Date: Wed, 11 Jun 2014 08:28:46 +0200 [thread overview]
Message-ID: <20140611062846.GZ15686@pengutronix.de> (raw)
In-Reply-To: <1402055461.188487416@f152.i.mail.ru>
Hi Alexander,
On Fri, Jun 06, 2014 at 03:51:01PM +0400, Alexander Shiyan wrote:
> Fri, 6 Jun 2014 06:36:50 +0200 от Sascha Hauer <s.hauer@pengutronix.de>:
> > On Thu, Jun 05, 2014 at 09:32:35PM +0400, Alexander Shiyan wrote:
> > > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> >
> > Applied, thanks
>
> Supplementary question.
> What's the plan to update dts branch?
> Can you update this branch together with the new release or the way it is?
My plan is (although it is not set in stone):
For every Kernel rc release merge the dts into barebox-next.
I don't want to merge directly into barebox-master so that we don't get
surprises in the master branch. This means that it can happen that we
end up with a dts from a rc1 Kernel in a barebox release which is not so
nice. I'll see what to do when this actually happens.
Sascha
--
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-06-11 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 17:32 Alexander Shiyan
2014-06-06 4:36 ` Sascha Hauer
2014-06-06 11:51 ` Alexander Shiyan
2014-06-11 6:28 ` Sascha Hauer [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=20140611062846.GZ15686@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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