[PATCH] Support for MSI MS-6156

[Uwe Hermann]

As everyone is committing new boards today, I don't want to be left behind.
So here goes one more board for today (yet-another-440BX).

Boot-tested to a Linux prompt successfully.

Kconfig only, I didn't bother adding oldconfig files anymore.

Uwe.

[Myles Watson]

On Tue, Oct 13, 2009 at 12:01 PM, Uwe Hermann  wrote:
> As everyone is committing new boards today, I don't want to be left behind.
> So here goes one more board for today (yet-another-440BX).
>
> Boot-tested to a Linux prompt successfully.

Looks good.  Only picky things:
1. You used spaces for indentation instead of tabs in devicetree.cb
     It looks good, but I think it's good to be standard.
> Kconfig only, I didn't bother adding oldconfig files anymore.

2.  The downside is that you don't get run with abuild, so if someone
breaks the build you won't know.  Of course it's similar enough to
other boards that most likely it won't happen.

Acked-by: Myles Watson

Thanks,
Myles

[Uwe Hermann]

On Tue, Oct 13, 2009 at 12:09:26PM -0600, Myles Watson wrote:
> On Tue, Oct 13, 2009 at 12:01 PM, Uwe Hermann  wrote:
> > As everyone is committing new boards today, I don't want to be left behind.
> > So here goes one more board for today (yet-another-440BX).
> >
> > Boot-tested to a Linux prompt successfully.
>
> Looks good.  Only picky things:
> You used spaces for indentation instead of tabs in devicetree.cb
>   It looks good, but I think it's good to be standard.

Yes, but I'd like to change that standard to "two spaces" in all
devicetree.cb files. Actually I sneaked in just that in all the boards
I added the last three years or so, and nobody noticed/complained ;-)

The Config.lb/devicetree.cb files can get _very_ convoluted and very
deeply nested, and one TAB for indentation (plus a comment on many
lines) make it _way_ to wide (definately lots more than 80 characters)
for my taste on many boards. Using two spaces looks much cleaner and
more readable in this case.

(This is an exception! I'm not proposing to do the same in C code or
the like. Only devicetree.cb!)
> > Kconfig only, I didn't bother adding oldconfig files anymore.
> The downside is that you don't get run with abuild, so if someone
>
> breaks the build you won't know.  Of course it's similar enough to
> other boards that most likely it won't happen.
>
> Acked-by: Myles Watson

Thanks, r4767. I added Config.lb et al for now to keep it in abuild,
but it shouldn't be required much longer, oldconfig will soon go away.

Uwe.

[Myles Watson]

> The Config.lb/devicetree.cb files can get _very_ convoluted and very
> deeply nested, and one TAB for indentation (plus a comment on many
> lines) make it _way_ to wide (definately lots more than 80 characters)
> for my taste on many boards. Using two spaces looks much cleaner and
> more readable in this case.

I agree that it looks better.  I'm a big fan of consistency, though,
so we should decide to make them all the same.
> (This is an exception! I'm not proposing to do the same in C code or
> the like. Only devicetree.cb!)

Sounds good to me.

Thanks,
Myles