From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot panasonic repo
Date: Thu, 18 Sep 2014 09:58:47 +0200 [thread overview]
Message-ID: <541A90B7.6010308@monstr.eu> (raw)
In-Reply-To: <201409180927.35918.marex@denx.de>
On 09/18/2014 09:27 AM, Marek Vasut wrote:
> On Thursday, September 11, 2014 at 07:18:00 AM, Masahiro Yamada wrote:
>> Hi Michal,
>
> Hi,
>
>> On Thu, 11 Sep 2014 06:56:04 +0200
>>
>> Michal Simek <monstr@monstr.eu> wrote:
>>> Hi,
>>>
>>> On 09/11/2014 05:09 AM, Masahiro Yamada wrote:
>>>> On Thu, 11 Sep 2014 01:33:20 +0200
>>>>
>>>> Marek Vasut <marex@denx.de> wrote:
>>>>> Hello,
>>>>>
>>>>> I'd be interested in maintaining u-boot-socfpga repository. So far, we
>>>>> don't have a repo for this platform and there is a large flurry of
>>>>> patches flying around without any kind of central point for them. I'd
>>>>> like to get your formal consent for starting this and if you agree,
>>>>> I'd start sending PR to Albert once the repo is in place.
>>>>
>>>> Me too. I'd like to own u-boot-uniphier to collect
>>>> Panasonic-SoC-specific changes.
>>>>
>>>> That would be faster and would not disturb Albert.
>>>
>>> I am not sure if you need to have separate repo to work like this.
>>> I am keeping zynq patches in my microblaze repo and sending pull request
>>> to Albert (or Tom now) and there is no problem with that.
>>
>> The point is that you collect Zynq-specific patches in your own place by
>> yourself and then send a pull-req to Albert or Tom, right?
>>
>> It does not matter whether it is a separate u-boot-zynq repo or
>> u-boot-microbraze/zynq branch.
>>
>>
>> I have sent the first series to add the core support of Panasonic SoCs
>> and boards (but it is taking much longer than I have expected)
>> and then I am planning to send more features and boards in the next phase.
>>
>>
>> What's the difference between what I want to do for Panasonic SoCs
>> and what you usually do for Zynq SoCs?
>
> [...]
>
> I fully support that we should have a repo for the panasonic socs, it's
> pointless to load Albert by making him apply patches by hand and you have
> proven numerous times that you do know what you're doing. I really see no
> blocker for doing this.
+1 on this if Masahiro wants to have separate repo.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140918/28da4c5b/attachment.pgp>
next prev parent reply other threads:[~2014-09-18 7:58 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 23:33 [U-Boot] u-boot-socfpga repository Marek Vasut
2014-09-11 3:09 ` Masahiro Yamada
2014-09-11 4:56 ` Michal Simek
2014-09-11 5:18 ` Masahiro Yamada
2014-09-18 7:27 ` [U-Boot] U-Boot panasonic repo Marek Vasut
2014-09-18 7:58 ` Michal Simek [this message]
2014-09-18 8:02 ` Marek Vasut
2014-09-18 8:24 ` Michal Simek
2014-09-18 10:13 ` Masahiro Yamada
2014-09-18 11:44 ` Albert ARIBAUD
2014-09-18 13:32 ` Masahiro YAMADA
2014-09-18 8:32 ` Wolfgang Denk
2014-09-18 8:43 ` Masahiro Yamada
2014-09-18 9:03 ` Wolfgang Denk
[not found] ` <CAMhH57QtP7H8rx8cq--s8HqeJFq+C4xmGhh1V2RB6CvDqOiiTg@mail.gmail.com>
2014-09-27 9:01 ` Masahiro YAMADA
2014-09-27 13:00 ` Wolfgang Denk
2014-09-27 15:02 ` Masahiro YAMADA
2014-09-27 15:57 ` Wolfgang Denk
2014-09-28 5:20 ` Masahiro YAMADA
2014-09-11 7:46 ` [U-Boot] u-boot-socfpga repository Wolfgang Denk
2014-09-11 7:55 ` Pavel Machek
2014-09-11 15:39 ` Marek Vasut
2014-09-11 16:01 ` Dinh Nguyen
2014-09-11 17:21 ` Marek Vasut
2014-09-16 9:56 ` Pavel Machek
2014-09-17 11:54 ` Chin Liang See
2014-09-19 9:54 ` Chin Liang See
2014-09-23 12:54 ` Tom Rini
2014-09-23 13:43 ` Wolfgang Denk
2014-09-23 13:46 ` Tom Rini
2014-09-23 14:30 ` Wolfgang Denk
2014-09-11 15:45 ` Marek Vasut
2014-09-11 16:14 ` Dinh Nguyen
2014-09-11 16:51 ` Marek Vasut
2014-09-11 23:14 ` Dinh Nguyen
2014-09-11 17:14 ` Tom Rini
2014-09-11 23:19 ` Dinh Nguyen
2014-09-12 5:25 ` Wolfgang Denk
2014-09-12 18:27 ` Dinh Nguyen
2014-09-12 19:46 ` Wolfgang Denk
2014-09-12 21:15 ` Dinh Nguyen
2014-09-12 22:14 ` Wolfgang Denk
2014-09-12 22:29 ` Dinh Nguyen
2014-09-12 22:51 ` Wolfgang Denk
2014-09-14 16:02 ` Dinh Nguyen
2014-09-14 16:46 ` Tom Rini
2014-09-15 1:07 ` Chin Liang See
2014-09-15 1:27 ` Marek Vasut
2014-09-15 1:43 ` Chin Liang See
2014-09-15 1:47 ` Marek Vasut
2014-09-14 16:51 ` Wolfgang Denk
2014-09-12 19:57 ` Michael Trimarchi
2014-09-12 21:05 ` David Hawkins
2014-09-12 21:20 ` Michael Trimarchi
2014-09-12 21:23 ` David Hawkins
2014-09-12 21:30 ` Michael Trimarchi
2014-09-12 21:32 ` Dinh Nguyen
2014-09-12 22:37 ` Wolfgang Denk
2014-09-15 1:35 ` Chin Liang See
2014-09-15 8:53 ` [U-Boot] mainline u-boot on socfpga Pavel Machek
2014-09-13 17:24 ` [U-Boot] u-boot-socfpga repository David Hawkins
2014-09-14 15:39 ` Dinh Nguyen
2014-09-14 16:30 ` Wolfgang Denk
2014-09-14 20:04 ` David Hawkins
2014-09-13 0:16 ` David Hawkins
2014-09-12 18:00 ` Michal Simek
2014-09-12 19:45 ` Wolfgang Denk
2014-09-11 15:46 ` Marek Vasut
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=541A90B7.6010308@monstr.eu \
--to=monstr@monstr.eu \
--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