From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/9] Added support for SPEAr SoCs
Date: Tue, 12 Jan 2010 07:38:39 -0600 [thread overview]
Message-ID: <4B4C7B5F.4090102@windriver.com> (raw)
In-Reply-To: <83d1d72b1001110913x54a59656ye8f8eddbbc61834c@mail.gmail.com>
Vipin Kumar wrote:
> Hello Tom,
>
>>>> I am planning to keep the patch order as it is but I would remove
>>>> dependencies eg. SPEAr600 would not contain code that depends on
>>>> a driver added later and so on.
>>>>
>>>> This should also be OK. Right?
>>> It should remove the 'git bisect' issue, which is the important thing to
>>> me. The way you did it in v3 should work, its just a bit uglier than
>>> doing it the "right" way that I outlined above. Eg you modify spear.h
>>> and config.mk each time you add a new driver, basically tweaking the
>>> board support as the patch sequence progresses instead of just adding
>>> proper board support in 1 patch at the end.
>>>
>>> Also, its a bit ugly to add both spear arch support as well as board
>>> support in patch 2/11. Ideally you'd have 1 patch adding spear
>>> architectural support, then additional patches for drivers, then patches
>>> for boards.
>>>
>> On 2/11, this patch must be split.
>> Arch support split from board support.
>>
>> Moving the driver support before board support would simplify the
>> review. The subsystem custodians would only have to review what they
>> are responsible for. I would also recommend doing this.
>>
>
> Changes done as you suggested in patch set version4
>
Thanks,
I am reviewing this patch set now.
So far it looks ok wrt mechanical checking.
Tom
> Regards
> Vipin
next prev parent reply other threads:[~2010-01-12 13:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 11:56 [U-Boot] [PATCH v2 0/9] Added support for SPEAr SoCs Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 1/9] Added README.spear Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 2/9] SPEAr600 SoC support added Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 3/9] SPEAr300 " Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 4/9] SPEAr310 " Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 5/9] SPEAr320 " Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 6/9] i2c driver support for SPEAr SoCs Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 7/9] smi " Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 8/9] nand(fsmc) " Vipin KUMAR
2010-01-07 11:56 ` [U-Boot] [PATCH v2 9/9] usbd " Vipin KUMAR
2010-01-09 9:50 ` Remy Bohmer
2010-01-07 16:42 ` [U-Boot] [PATCH v2 0/9] Added " Tom
2010-01-07 18:03 ` Armando VISCONTI
2010-01-08 13:28 ` Vipin KUMAR
2010-01-07 18:21 ` Peter Tyser
2010-01-08 4:35 ` Vipin KUMAR
2010-01-08 15:55 ` Peter Tyser
2010-01-08 16:43 ` Tom
2010-01-11 17:13 ` Vipin Kumar
2010-01-12 13:38 ` Tom [this message]
2010-01-08 13:31 ` Vipin KUMAR
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=4B4C7B5F.4090102@windriver.com \
--to=tom.rix@windriver.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