From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2] socfpga: Move board/socfpga_cyclone5 to board/socfpga
Date: Tue, 9 Jul 2013 10:57:40 +0200 [thread overview]
Message-ID: <20130709105740.22ecd96c@lilith> (raw)
In-Reply-To: <20130708232201.GA17631@amd.pavel.ucw.cz>
Hi Pavel,
On Tue, 9 Jul 2013 01:22:01 +0200, Pavel Machek <pavel@denx.de> wrote:
> Hi!
>
> > > > > From: Dinh Nguyen <dinguyen@altera.com>
> > > > >
> > > > > Because the SOCFPGA platform will include support for Cyclone V and
> > > > > Arria V FPGA parts, renaming socfpga_cyclone5 folder to socfpga to
> > > > > be more generic.
> > > > >
> > > > > Signed-off-by: Dinh Nguyen <dinguyen@altera.com>
> > > > > Reviewed-by: Pavel Machek <pavel@denx.de>
> > > > > Cc: Chin Liang See <clsee@altera.com>
> > > > > Cc: Wolfgang Denk <wd@denx.de>
> > > > > CC: Pavel Machek <pavel@denx.de>
> > > > > Cc: Tom Rini <trini@ti.com>
> > > > >
> > > > > v2:
> > > > > - Add Reviewed-by: Pavel Machek
> > > > > - Cc: Tom Rini
> > > > > ---
> > > >
> > > > Do you really mean that V2 is the exact same code as V1? If it is, then
> > > > V2 is unneeded. And if V2 is different from V1, then history should
> > > > tells us the difference(s).
> > >
> > > V2 is the same as v1 codewise. So should I resend this a V1 to be
> > > applied?
> >
> > If V1 is the same as V2 as far as the code is concerned, then there is
> > simply no point in sending V2 or resending V1 again.
> >
> > The V2 history makes me guess you thought it necessary to officialize
> > Pavel's Reviewed-By somehow, but that's unneeded; patchworks takes care
> > of collecting all the {Reviewed,Acked,Tested,...}-by's and providing
> > them when applying the patch through pwclient.
>
> This got pretty confusing lately. Can we just wait for the patches to
> be applied, or do we need to take some action?
No, no need to take action; I was just clarifying why V2 was unneeded
here, so that similar uneeded new versions are avoided in the future.
Since V1 has already been marked as superseded, I'll apply V2 -- after
2013.07 is out.
> Thanks,
> Pavel
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-07-09 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 22:00 [U-Boot] [PATCHv2] socfpga: Move board/socfpga_cyclone5 to board/socfpga dinguyen at altera.com
2013-07-05 21:04 ` Albert ARIBAUD
2013-07-08 16:10 ` Dinh Nguyen
2013-07-08 20:01 ` Albert ARIBAUD
2013-07-08 23:22 ` Pavel Machek
2013-07-09 8:57 ` Albert ARIBAUD [this message]
2013-07-25 8:56 ` Albert ARIBAUD
-- strict thread matches above, loose matches on Subject: below --
2013-07-02 20:18 dinguyen at altera.com
2013-07-02 21:49 ` Wolfgang Denk
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=20130709105740.22ecd96c@lilith \
--to=albert.u.boot@aribaud.net \
--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