All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	roger blofeld <blofeldus@yahoo.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Video Card to Lite5200
Date: Sat, 01 Jul 2006 19:29:39 +1000	[thread overview]
Message-ID: <1151746179.19419.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20060701091507.EA1F4352681@atlas.denx.de>

On Sat, 2006-07-01 at 11:15 +0200, Wolfgang Denk wrote:
> In message <1151709367.27137.4.camel@localhost.localdomain> you wrote:
> >
> > > I don;t know - the patches were submitted to this list  a  long  time
> > > ago; we added them to our repository without any additional problems;
> > > see http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git
> > 
> > Any reason why you keep that repository instead of submiting the patches
> > for proper upstream inclusion or to linuxppc-dev at least ?
> 
> We submit patches every now and then, as time permits.  My  intention
> is to keep the differences between our tree and kernel.org minimal.
> 
> But you know how this goes: just adding support for a new board means
> sending patches to the linuxppc_dev, mtd, i2c, usb,  lm_sensors,  ...
> mailing  lists. Then you have to wait some time, then you resend. and
> you have to keep track of all these things.  And  the  board  support
> will  not  work  before the last piece of the puzze has been accepted
> and merged and pushed upstream. All this takes a lot  of  effort  and
> even  more  calendar time. We need a way to provide a solution to our
> customers fast - that's why we maintain our own development branch.
> 
> I'd be happy if you could recommend a better approach to handle this.

Oh, it's fine to maintain a dev. branch, but I haven't seen you submit
stuff to linuxppc-dev for some time so I wanted to make sure you were
still on track :)

Ben.

  reply	other threads:[~2006-07-01  9:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 19:30 Video Card to Lite5200 Alan Carvalho
2005-12-05 20:35 ` Wolfgang Denk
2005-12-05 20:39   ` Alessandro Rubini
2005-12-07 17:23     ` roger blofeld
2005-12-07 18:53       ` Alan Carvalho
2005-12-07 19:51       ` Wolfgang Denk
2005-12-13 18:10         ` MPC5200 RTC bennett78
2006-06-30 23:16         ` Video Card to Lite5200 Benjamin Herrenschmidt
2006-07-01  9:15           ` Wolfgang Denk
2006-07-01  9:29             ` Benjamin Herrenschmidt [this message]
2005-12-08  0:25       ` Alessandro Rubini
2005-12-08  5:59       ` White
2005-12-08 23:10         ` Wolfgang Denk
2005-12-09 11:49           ` Andrey Volkov
2005-12-07 21:23   ` bennett78
2005-12-07 22:53     ` Wolfgang Denk
     [not found] <dc70db7d0512060906y7fa62c56q4c25dd5d92b2b2dd@mail.gmail.com>
     [not found] ` <20051206203343.67682353F5E@atlas.denx.de>
2005-12-08 13:18   ` Alan Carvalho
2005-12-08 23:14     ` Wolfgang Denk

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=1151746179.19419.0.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=blofeldus@yahoo.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wd@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 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.