linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, kyle@mcmartin.ca,
	"Gala Kumar K.-galak" <galak@freescale.com>,
	linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH 00/14] ppc32: Remove board ports that are no longer maintained
Date: Fri, 29 Jul 2005 12:33:33 -0400	[thread overview]
Message-ID: <5027.1122654813@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Kumar Gala <kumar.gala@freescale.com> of "Wed, 27 Jul 2005 18:34:23 CDT." <3965D4DD-1628-4463-890F-106DB5BC6931@freescale.com>

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Kumar" == Kumar Gala <kumar.gala@freescale.com> writes:
    >> When we recover our history from the linuxppc-2.4/2.5 trees we
    >> can show exactly how long it's been since anybody touched ep405.
    >> 
    >> Quick googling shows that it's been almost 2 years since the last
    >> mention of ep405 (exluding removal discussions) on
    >> linuxppc-embedded.  Last ep405-related commits are more than 2
    >> years ago.

  So, I'll bet I can find other parts of the kernel tree that haven't
been touched in 2 years.  Maybe there isn't anything to fix?

  Happens that in our case,
	  a) the board is the basis to our own board.
	  b) we only moved to 2.6 in May.

  So, I just don't get removing board support files.

- -- 
] Michael Richardson          Xelerance Corporation, Ottawa, ON |  firewalls  [
] mcr @ xelerance.com           Now doing IPsec training, see   |net architect[
] http://www.sandelman.ca/mcr/    www.xelerance.com/training/   |device driver[
]                    I'm a dad: http://www.sandelman.ca/lrmr/                 [
  
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQupaXIqHRg3pndX9AQFnGQP+JXX0ZTKW35LljC/ighUPpmcdClRlmWP2
fsnofXYNi2v9QEkYpoS8pHMc3ClKHT8MFzK/nsDe1CFWPxxavK+365usf77DSGWB
bjZ8CZWjkvDt7IMjBxEnSlzCTVt39Gtjq1zM/DMY0SOi1ccB7TIZE+1Ol3zkYnW5
2X6+0SKgS6Q=
=kcQj
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-29 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 15:32 [PATCH 00/14] ppc32: Remove board ports that are no longer maintained Kumar Gala
2005-07-27 16:13 ` Michael Richardson
2005-07-27 16:27   ` Eugene Surovegin
2005-07-27 17:15     ` Matt Porter
2005-07-27 23:34       ` Kumar Gala
2005-07-29 16:33         ` Michael Richardson [this message]
2005-07-29 17:03       ` Esben Nielsen
2005-07-29 18:10         ` Kumar Gala
2005-07-27 19:57 ` Andrew Morton
2005-07-27 23:35   ` Kumar Gala
2005-07-31 16:39   ` Kumar Gala
2005-08-30  1:46   ` Kumar Gala
2005-08-30  7:44     ` Eugene Surovegin

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=5027.1122654813@marajade.sandelman.ottawa.on.ca \
    --to=mcr@sandelman.ottawa.on.ca \
    --cc=akpm@osdl.org \
    --cc=galak@freescale.com \
    --cc=kumar.gala@freescale.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).