public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Darwin Rambo <drambo@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] Introducing the Broadcom bcm281xx Architecture
Date: Thu, 30 Jan 2014 15:12:20 -0800	[thread overview]
Message-ID: <52EADC54.2000103@broadcom.com> (raw)
In-Reply-To: <20140129223210.GV3277@bill-the-cat>



On 14-01-29 02:32 PM, Tom Rini wrote:
> On Mon, Jan 27, 2014 at 10:53:24AM -0800, Darwin Rambo wrote:
> 
>> This patchset introduces the Broadcom bcm281xx family of mobile SoC 
>> chips. Broadcom kona hardware blocks are often found in Broadcom mobile
>> SoC chips including the bcm281xx family, so support for some of these 
>> kona blocks is also provided here. These patches work on u-boot master
>> as well as the u-boot-arm custodian tree.
>>
>> Darwin Rambo (6):
>>   arch: kona: Initial commit of kona-common architecture code
>>   arch: bcm281xx: Initial commit of bcm281xx architecture code
>>   gpio: kona: Add Kona gpio driver
>>   i2c: kona: Add Kona I2C driver
>>   mmc: kona: Add Kona mmc driver
>>   board: bcm28155_ap: Add board files
> 
> Thanks for posting.  Globally, please don't introduce another style for
> the file header,
> /*
>  * This works
>  * just fine.
>  *
>  * Including what the file is about
>  */
OK - legacy stuff will be fixed.

> 
> And I also see the incorrect style sprinkled throughout.
> 
> I saw some '#define<tab>' mixed in with '#define<space>', and some other
> things I'd have sworn checkpatch complains about, so please make sure
> things are checkpatch clean (except for very long printed strings, which
> are an exception to line length rules).
Well, checkpatch was clean, so I think there's a problem with the tool.
Another minor gripe is that checkpatch and "indent -linux" don't agree
on everything, "int * foo" being one of them. :)
> 
> Finally, please CC the custodians for i2c/mmc for those drivers as they
> may have further comments than the above list.
OK. There are mmc, i2c and gpio drivers. I assume each driver gets a
different CC:?
> 
> Thanks!
> 
Thanks to you too!

  reply	other threads:[~2014-01-30 23:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 18:53 [U-Boot] [PATCH 0/6] Introducing the Broadcom bcm281xx Architecture Darwin Rambo
2014-01-27 18:53 ` [U-Boot] [PATCH 1/6] arch: kona: Initial commit of kona-common architecture code Darwin Rambo
2014-01-29 22:32   ` Tom Rini
2014-01-30 23:09     ` Darwin Rambo
2014-01-27 18:53 ` [U-Boot] [PATCH 2/6] arch: bcm281xx: Initial commit of bcm281xx " Darwin Rambo
2014-01-29 22:32   ` Tom Rini
2014-01-30 22:03     ` Darwin Rambo
2014-01-31 17:54       ` Tom Rini
2014-01-31 18:19         ` Darwin Rambo
2014-01-31 17:47     ` Matt Porter
2014-01-27 18:53 ` [U-Boot] [PATCH 3/6] gpio: kona: Add Kona gpio driver Darwin Rambo
2014-01-27 18:53 ` [U-Boot] [PATCH 4/6] i2c: kona: Add Kona I2C driver Darwin Rambo
2014-01-27 18:53 ` [U-Boot] [PATCH 5/6] mmc: kona: Add Kona mmc driver Darwin Rambo
2014-01-27 18:53 ` [U-Boot] [PATCH 6/6] board: bcm28155_ap: Add board files Darwin Rambo
2014-01-29 22:33   ` Tom Rini
2014-01-30 23:05     ` Darwin Rambo
2014-01-31 14:17       ` Tom Rini
2014-01-31 17:05         ` Tim Kryger
2014-01-31 17:15           ` Tom Rini
2014-01-31 18:18             ` Darwin Rambo
2014-01-29 22:32 ` [U-Boot] [PATCH 0/6] Introducing the Broadcom bcm281xx Architecture Tom Rini
2014-01-30 23:12   ` Darwin Rambo [this message]
2014-01-31 19:14     ` 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=52EADC54.2000103@broadcom.com \
    --to=drambo@broadcom.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