public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/7] arm: vf610: Add Vybrid VF610 CPU support
Date: Fri, 31 May 2013 10:59:03 +0200	[thread overview]
Message-ID: <51A86657.8090000@denx.de> (raw)
In-Reply-To: <1005281327.1323573.1369838796215.JavaMail.root@advansee.com>

On 29/05/2013 16:46, Beno?t Th?baudeau wrote:
> Hi Alison,
> 

Hi Benoit,

>>> I have just noticed that this was actually in 6/7. Why are you putting
>>> this into a separate patch?
>> [Alison Wang] Because patch 2/7 is about VF610 CPU support, and
>> doc/README.vf610 is also a document about
>> VF610 SoC. Doc/README.mxc_ocotp is the document about a driver (IP OCOTP), so
>> this driver document should be
>> separated from CPU patch 2/7.
> 
> I don't think so: It's part of what comes with the addition of the VF610
> platform, so 6/7 could be merged into 2/7. But it does not really matter. It's
> probably also fine if you keep what you did.
> 
> Stefano, any opinion?

Strictly speaking, you're right. But as you mentioned, it does not
really matter. Without reposting, I can myself squash 6/7 into 2/7 by
merging the patchset.

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

  reply	other threads:[~2013-05-31  8:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  8:55 [U-Boot] [PATCH v4 0/7] arm: vf610: Add Freescale Vybrid VF610 CPU and VF610TWR board support Alison Wang
2013-05-28  8:55 ` [U-Boot] [PATCH v4 1/7] arm: vf610: Add IOMUX support for Vybrid VF610 Alison Wang
2013-05-28 18:57   ` Benoît Thébaudeau
2013-05-29  5:29     ` Wang Huan-B18965
2013-05-29  6:21       ` Stefano Babic
2013-05-29 14:54         ` Benoît Thébaudeau
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 2/7] arm: vf610: Add Vybrid VF610 CPU support Alison Wang
2013-05-28 19:16   ` Benoît Thébaudeau
2013-05-28 19:30     ` Benoît Thébaudeau
2013-05-29  5:37       ` Wang Huan-B18965
2013-05-29 14:46         ` Benoît Thébaudeau
2013-05-31  8:59           ` Stefano Babic [this message]
2013-05-31 16:10             ` Benoît Thébaudeau
2013-05-29  5:32     ` Wang Huan-B18965
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 3/7] net: fec_mxc: Add support for Vybrid VF610 Alison Wang
2013-05-28 19:21   ` Benoît Thébaudeau
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 4/7] arm: vf610: Add watchdog " Alison Wang
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 5/7] arm: vf610: Add uart " Alison Wang
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 6/7] arm: vf610: Add Vybrid VF610 to mxc_ocotp document Alison Wang
2013-05-31 16:10   ` Benoît Thébaudeau
2013-06-03  9:03   ` Stefano Babic
2013-05-28  8:55 ` [U-Boot] [PATCH v4 7/7] arm: vf610: Add basic support for Vybrid VF610TWR board Alison Wang
2013-05-28 19:57   ` Benoît Thébaudeau
2013-05-29  5:52     ` Wang Huan-B18965
2013-05-29 14:49       ` Benoît Thébaudeau
2013-06-03  9:03   ` Stefano Babic

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=51A86657.8090000@denx.de \
    --to=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /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