From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 03/14] arm/km: convert mgcoge3un target to km_kirkwood
Date: Thu, 05 Jul 2012 07:54:13 +0200 [thread overview]
Message-ID: <4FF52C05.6090308@keymile.com> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2FE3057C@SC-VEXCH4.marvell.com>
On 07/04/2012 11:21 AM, Prafulla Wadaskar wrote:
>
>
>> -----Original Message-----
>> From: Wolfgang Denk [mailto:wd at denx.de]
>> Sent: 03 July 2012 23:31
>> To: Prafulla Wadaskar
>> Cc: Holger Brunck; u-boot at lists.denx.de; Valentin Longchamp
>> Subject: Re: [U-Boot] [PATCH v2 03/14] arm/km: convert mgcoge3un
>> target to km_kirkwood
>>
>> Dear Prafulla,
>>
>> In message <F766E4F80769BD478052FB6533FA745D1A2FE3028D@SC-
>> VEXCH4.marvell.com> you wrote:
>>>
>>> Do you think I should pull this patch series, I hope it applies
>> cleanly on the recent master branch.
>>> Please confirm.
>>
>> I have to admit that I neither reviewed the patches in question, nor
>> did I follow the whole thread of communication in this patch series.
>> But the general rule is that if there are no strong argumentents
>> against a patch (like a clear NAK or a specific request for changes)
>> we will apply it.
>
> Hi Wolfgang,
> This patch series was too old, I was trying to save my effors ;-D
> Finally I pulled these patches and tried to apply, but as I doubted it failed :-(
>
> Hi Hogler
>
> I could not apply the said patch series to the latest u-boot-marvell.git master branch
>
> Pls re-submit it.
>
> git-am U-Boot-1-9-arm-km-add-board-type-to-boards.cfg.patch
>
> Applying arm/km: add board type to boards.cfg
>
> error: patch failed: boards.cfg:138
> error: boards.cfg: patch does not apply
> error: patch failed: include/configs/km_kirkwood.h:42
> error: include/configs/km_kirkwood.h: patch does not apply
> Patch failed at 0001.
> When you have resolved this problem run "git-am --resolved".
> If you would prefer to skip this patch, instead run "git-am --skip"
>
sorry but now I am completely confused. Here you say you want to apply 01-09
which includes
[PATCH v2 05/14] arm/km: correct init of 88e6352 switch in the reset_phy function
and
[PATCH v2 09/14] arm/km: add support for external switch configuration
this includes basic infrastructure for the managed switch.
In another thread you NAK the whole driver:
http://lists.denx.de/pipermail/u-boot/2012-July/127529.html
In a further different thread where I asked if I should provide updates which
apply cleanly you say no there are general updates needed:
http://lists.denx.de/pipermail/u-boot/2012-July/127531.html
For me these statements are conflicting.
So can you please state clearly which updates you request from myside for which
patch and which are from your point of view not acceptable and why? Thanks
Regards
Holger
next prev parent reply other threads:[~2012-07-05 5:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 13:33 [U-Boot] [PATCH v2 00/14] updates for Keymile Marvell boards Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 01/14] arm/km: add kmnusa board support Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 02/14] arm/km: add kmcoge5un " Holger Brunck
2012-07-03 8:04 ` Prafulla Wadaskar
2012-07-03 9:37 ` Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 03/14] arm/km: convert mgcoge3un target to km_kirkwood Holger Brunck
2012-07-03 8:05 ` Prafulla Wadaskar
2012-07-03 10:37 ` Holger Brunck
2012-07-03 11:19 ` Prafulla Wadaskar
2012-07-03 12:31 ` Holger Brunck
2012-07-03 12:38 ` Prafulla Wadaskar
2012-07-03 13:00 ` Holger Brunck
2012-07-03 13:07 ` Prafulla Wadaskar
2012-07-03 13:43 ` Holger Brunck
2012-07-03 14:39 ` Prafulla Wadaskar
2012-07-03 18:00 ` Wolfgang Denk
2012-07-04 9:21 ` Prafulla Wadaskar
2012-07-05 5:54 ` Holger Brunck [this message]
2012-07-05 6:04 ` Prafulla Wadaskar
2012-07-05 7:15 ` Holger Brunck
2012-07-05 12:09 ` Prafulla Wadaskar
2012-07-05 13:43 ` Holger Brunck
2012-07-05 13:48 ` Prafulla Wadaskar
2012-07-05 15:44 ` Holger Brunck
2012-07-04 8:24 ` Holger Brunck
2012-07-04 9:23 ` Prafulla Wadaskar
2012-07-03 14:00 ` Detlev Zundel
2012-06-13 13:33 ` [U-Boot] [PATCH v2 04/14] arm/km: remove portl2.h and use km_kirkwood instead Holger Brunck
2012-07-03 8:12 ` Prafulla Wadaskar
2012-06-13 13:33 ` [U-Boot] [PATCH v2 05/14] arm/km: correct init of 88e6352 switch in the reset_phy function Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 06/14] arm/km: enable BOCO2 FPGA download support Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 07/14] arm/km: cleanup km_kirkwood boards Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 08/14] arm/km: redefine piggy 4 reg names to avoid conflicts Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 09/14] arm/km: add support for external switch configuration Holger Brunck
2012-06-26 15:31 ` [U-Boot] [PATCH v3 " Valentin Longchamp
2012-06-13 13:33 ` [U-Boot] [PATCH v2 10/14] arm/km: enable external switch configuration for kmnusa Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 11/14] arm/km: skip FPGA config when already configured Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 12/14] arm/km: support the 2 PCIe fpga resets Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 13/14] arm/km: add implementation for read_dip_switch Holger Brunck
2012-06-13 13:33 ` [U-Boot] [PATCH v2 14/14] arm/km: remove calls to kw_gpio_* in board_early_init_f Holger Brunck
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=4FF52C05.6090308@keymile.com \
--to=holger.brunck@keymile.com \
--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