From: "David H. Lynch Jr." <dhlii@dlasys•net>
To: Wolfgang Reissnegger <wolfgang.reissnegger@xilinx•com>
Cc: linuxppc-dev@ozlabs•org,
Andrei Konovalov <akonovalov@ru•mvista.com>,
linuxppc-embedded@ozlabs•org
Subject: Re: Xilinx git tree at source.mvista.com
Date: Thu, 24 May 2007 21:49:53 -0400 [thread overview]
Message-ID: <465640C1.1060206@dlasys.net> (raw)
In-Reply-To: <20070524154211.169C7AE8051@mail10-fra.bigfish.com>
Wolfgang Reissnegger wrote:
> Hi Andrei, David,
>
> It's great to hear that Andrei's git tree is active again.
>
> As you might have heard, Xilinx is in the process of setting up a git
> tree as well. Right now we are waiting for the new hosting machines to
> be installed. We should get those machines up and running shortly
> (within a couple weeks).
>
Absolutely fantastic - however I think kernel.org would be happy to host
your git tree for you
as well as a few other places. Those are locations people would look for
public git trees.
I beleive you can still excecise some control. I beleive they are free -
though I suspect kernel.org would not
mind contributions from xilinx.
>
> Currently the tree is based on mainline and adds support for MicroBlaze.
> I also intent to merge Grant Likely's virtex-dev branch, the framebuffer
> patch and the various other contributions that are out there.
>
You might want to look at the Microbalze-uClinux mailing list as well as
petalogix.
They are not using git yet, but they are puching the microblaze towards
kernel org
inclusion.
> We are also in the process of changing our internal coding guidelines to
> match the common Linux style (e.g. u32, u16 types, 8 char wide (tab)
> indentation, curly brace location etc) to make it easier to integrate
> code into the kernel and push it upstream.
>
For me the most significant issue is the bazillion layers of nested
macro's and includes.
The kernel style guides atleast to me are primarily about the
readability and understandability of the code.
not where the curly brackets are.
> I'll send an update once we have the server up and running.
>
> Thanks,
> Wolfgang
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys•net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2007-05-25 1:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 8:53 Xilinx git tree at source.mvista.com Andrei Konovalov
2007-05-24 9:57 ` David H. Lynch Jr.
2007-05-24 13:08 ` Andrei Konovalov
2007-05-24 15:42 ` Wolfgang Reissnegger
2007-05-25 1:49 ` David H. Lynch Jr. [this message]
2007-05-25 4:26 ` Wolfgang Reissnegger
2007-05-28 23:30 ` John Williams
2007-05-29 8:07 ` Andrei Konovalov
2007-05-25 0:47 ` David H. Lynch Jr.
2007-06-12 10:29 ` Esben Nielsen
2007-06-12 17:09 ` Dale Farnsworth
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=465640C1.1060206@dlasys.net \
--to=dhlii@dlasys$(echo .)net \
--cc=akonovalov@ru$(echo .)mvista.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=wolfgang.reissnegger@xilinx$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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