mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4 0/5] ARM: add support for Zynq
Date: Tue, 26 Mar 2013 10:38:25 +0100	[thread overview]
Message-ID: <CAHTX3d+2H+T9xK94con4mGzbT=LuCK_288ceQ5jtSYfv1u5nhQ@mail.gmail.com> (raw)
In-Reply-To: <20130326093321.GA18836@pengutronix.de>

2013/3/26 Steffen Trumtrar <s.trumtrar@pengutronix.de>:
> On Tue, Mar 26, 2013 at 10:21:01AM +0100, Michal Simek wrote:
>> Hi Steffen,
>>
>> On 03/26/2013 10:11 AM, Steffen Trumtrar wrote:
>> >Hi!
>> >
>> >This is mostly a repost of v3. Only changes are in 4/5.
>> >The final image now gets always piped through zynq_mkimage. This is needed
>> >anyway, so do it always.
>> >This tool will eventually replace all the flash_header linker stuff, although
>> >it is pretty simple on the Zynq.
>>
>> I have signed to barebox mailing list today and I see that in the right time.
>> It is little bit messy what you have sent.
>> It is mix of v2/v3/v4 patches where it is not clear which version I should try.
>>
>> Can you please resend the whole patchset as v5?
>>
>
> Hi,
>
> I'm actually not sure if I like the mix myself, but you gotta try stuff :-)
> The series is the latest and greatest and some patches just didn't change.
> But it seems to confuse more than it helps.
> So, just take the series as is, please. Sascha is okay with the patches and
> will take them (I hope he doesn't change his mind in the meantime :-))
> Sorry for the confusion.

Interesting working style. From my point of view this is really problematic
because you it is just confusing. But ok if others are ok with this workflow.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-03-26  9:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  9:11 Steffen Trumtrar
2013-03-26  9:11 ` [PATCH v3 1/5] serial: Add driver for Cadence UART Steffen Trumtrar
2013-03-26  9:11 ` [PATCH v3 2/5] ARM: zynq: Add new architecture zynq Steffen Trumtrar
2013-03-26 13:19   ` Josh Cartwright
2013-03-26 13:28     ` Steffen Trumtrar
2013-03-26  9:11 ` [PATCH v2 3/5] ARM: zynq: add clk support for zynq7000 Steffen Trumtrar
2013-03-26 13:20   ` Josh Cartwright
2013-03-26 13:25     ` Josh Cartwright
2013-03-26 14:20       ` Michal Simek
2013-03-26  9:11 ` [PATCH v3 4/5] ARM: zynq: add zynq fsbl checksum script Steffen Trumtrar
2013-03-26  9:11 ` [PATCH v3 5/5] ARM: zynq: Add support for the Avnet Zedboard Steffen Trumtrar
2013-03-26  9:21 ` [PATCH v4 0/5] ARM: add support for Zynq Michal Simek
2013-03-26  9:33   ` Steffen Trumtrar
2013-03-26  9:38     ` Michal Simek [this message]
2013-03-26 10:22   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-27  8:32 ` Sascha Hauer

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='CAHTX3d+2H+T9xK94con4mGzbT=LuCK_288ceQ5jtSYfv1u5nhQ@mail.gmail.com' \
    --to=monstr@monstr.eu \
    --cc=barebox@lists.infradead.org \
    --cc=s.trumtrar@pengutronix.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