From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] m68k: generic board
Date: Thu, 19 Feb 2015 22:41:04 +0100 [thread overview]
Message-ID: <54E65870.4090305@sysam.it> (raw)
In-Reply-To: <20150206160254.GU10826@bill-the-cat>
On 06/02/2015 17:02, Tom Rini wrote:
> On Mon, Jan 26, 2015 at 09:39:13AM +0000, Huan Wang wrote:
>> Hi, Tom,
>>
>>> On Thu, Jan 15, 2015 at 04:08:40PM +0100, Angelo Dureghello wrote:
>>>> Dear all,
>>>>
>>>> i would like to post a patch with the m68k generic board support,
>>>> tested and working here, but of course not tested for all the other
>>>> m68k boards except mine.
>>>>
>>>> My coldfire board is the "amcore" board not yet accepted.
>>>>
>>>> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/193661
>>>> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/193660
>>>>
>>>> I need some suggestions on how to proceed now.
>>>>
>>>> I already modified my board config to work with generic board support.
>>>>
>>>> So my thought is to post 2 separate patches:
>>>> 1
>>>> - add generic board (1/1). Each board maintainer should then test it
>>>> and report for feedbacks.
>>>> 2
>>>> Re-post a 2/2 patch (v8) of amcore using generic board:
>>>> - amcore board (1),
>>>> - mcf5307 support (2),
>>>>
>>>> This amcore board is the coldfire base i use here for all the general
>>>> m68k tests.
>>>>
>>>> With your help commenting on this patch until it is conformant to the
>>>> last recent coding guidelines could help me and Alison to know what
>>>> has to be purged / changed, (eventually, if needed) in all other m68k
>>>> boards code.
>>>>
>>>> What do you think ?
>>>
>>> Lets go with #2 and we'll purge the rest of the boards that you don't
>>> want to convert and compile test after -rc1. Thanks!
>>>
>> [Alison Wang] Do you mean you will purge the rest of the boards if
>> they are not converted and tested?
>>
>> I have these boards, such as m52277evb, m5253demo, m53017evb,
>> m5329evb, m5373evb, m54418twr, m54451evb, m54455evb, m547xevb and
>> m548xevb. I think I really need some time to convert and test them.
>
> Please get them converted ASAP and remove the rest of the boards which
> you do not plan to support. Thanks!
Dear Tom and all,
so basically, i posted a patch with with 1 and 2 together, since
"amcore" board and m68k generic-board additions was connected.
Alison then added some changes over my generic-board patch.
What is now the correct way to proceed, as m68k custodians ? We need to
wait for feedbacks/ack on the patches or, at what stage could we apply
this patches into the u-boot-coldfire repo ?
Thanks,
Best regards,
Angelo Dureghello
next prev parent reply other threads:[~2015-02-19 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 15:08 [U-Boot] [RFC] m68k: generic board Angelo Dureghello
2015-01-23 21:29 ` Tom Rini
2015-01-26 9:39 ` Huan Wang
2015-02-06 16:02 ` Tom Rini
2015-02-06 21:49 ` Angelo Dureghello
2015-02-19 21:41 ` Angelo Dureghello [this message]
2015-02-24 20:47 ` Tom Rini
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=54E65870.4090305@sysam.it \
--to=angelo@sysam.it \
--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