From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Kevin Hickey <khickey@rmicorp.com>,
Linux-MIPS <linux-mips@linux-mips.org>,
Florian Fainelli <florian@openwrt.org>,
Bruno Randolf <bruno.randolf@4g-systems.biz>
Subject: Re: [PATCH 2/3] Alchemy: Move evalboard code to common directory
Date: Wed, 12 Nov 2008 13:38:29 +0300 [thread overview]
Message-ID: <491AB225.1010005@ru.mvista.com> (raw)
In-Reply-To: <20081112060630.GB9358@roarinelk.homelinux.net>
Hello.
Manuel Lauss wrote:
>> And in keeping with my other email, I think that the evalboards
>> directory is a good idea (though I would recommend the name
>> "develboards" as that is what DB stands for), but it should contain
>> subdirectories for each board and a common directory for common DB code.
>> Smashing all of the board code into one file doesn't leave any room to
>> grow if that file gets too big. Also, a single common.c will not be
>> sufficient in the future.
>>
>
> Okay, I'll change that, test and resend.
>
> Thanks,
> Manuel Lauss
>
[...]
>>> Move all code of the Pb/Db boards to a single subdirectory and extract
>>> some common code.
>>>
>>> Signed-off-by: Manuel Lauss <mano@roarinelk.homelinux.net>
>>>
I see you, Manuel is no better. :-)
Please avoid leaving unquoted patch behind your reply.
WBR, Sergei
next prev parent reply other threads:[~2008-11-12 10:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 12:08 [PATCH 0/3] Alchemy: consolidate board code, v2 Manuel Lauss
2008-11-08 12:08 ` [PATCH 1/3] Alchemy: merge small board files into single files Manuel Lauss
2008-11-12 3:54 ` Kevin Hickey
2008-11-12 6:05 ` Manuel Lauss
2008-11-08 12:08 ` [PATCH 2/3] Alchemy: Move evalboard code to common directory Manuel Lauss
2008-11-12 4:00 ` Kevin Hickey
2008-11-12 6:06 ` Manuel Lauss
2008-11-12 10:38 ` Sergei Shtylyov [this message]
2008-11-12 10:55 ` Sergei Shtylyov
2008-11-12 10:35 ` Sergei Shtylyov
2008-11-12 12:05 ` Manuel Lauss
2008-11-12 13:39 ` Kevin Hickey
2008-11-12 13:38 ` Kevin Hickey
2008-11-12 15:45 ` Maciej W. Rozycki
2008-11-12 15:52 ` Sergei Shtylyov
2008-11-12 16:16 ` Maciej W. Rozycki
2008-11-12 16:20 ` Sergei Shtylyov
2008-11-08 12:08 ` [PATCH 3/3] Alchemy: allow boards to override default reset/poweroff functions Manuel Lauss
-- strict thread matches above, loose matches on Subject: below --
2008-11-07 18:41 [PATCH 0/3] Alchemy: consolidate board code Manuel Lauss
2008-11-07 18:41 ` [PATCH 1/3] Alchemy: merge small board files into single files Manuel Lauss
[not found] ` <cover.1226083170.git.mano@roarinelk.homelinux.net>
2008-11-07 18:41 ` [PATCH 2/3] Alchemy: Move evalboard code to common directory Manuel Lauss
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=491AB225.1010005@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bruno.randolf@4g-systems.biz \
--cc=florian@openwrt.org \
--cc=khickey@rmicorp.com \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.