From: Ralf Baechle <ralf@linux-mips.org>
To: "Koeller, T." <Thomas.Koeller@baslerweb.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Remove Basler Excite support
Date: Tue, 6 Feb 2007 11:03:58 +0000 [thread overview]
Message-ID: <20070206110358.GA29286@linux-mips.org> (raw)
In-Reply-To: <C5A8FDEFF7647F4C9CB927D7DEB3077303FCF2C9@ahr075s.basler.corp>
On Mon, Feb 05, 2007 at 11:35:55AM +0100, Koeller, T. wrote:
> the last time I worked on it (which is three days ago, while working to make the excite nand flash driver ready for submission), it built and ran just fine, so I really wonder why you are removing it. I now notice that it has been made depending on BROKEN some time ago, which escaped my attention when it happened.
It was marked broken because in the incomplete merge state it did not
build.
My last emails did not receive any answer and the patch to remove it has
actually been sitting in the queue tree for well over a month mostly as
hint by waiving with a tree trunk so I did interpret this as a loss of
communication.
> The reason I did not encounter any build problems is that I always built the code with the yet-to-be-submitted drivers. The compilation error you get when building the excite platform is caused by a dependency upon the rm9k_serial driver, on which the platform depends for serial console support. I haven't yet managed to submit that driver, although I made several attempts. If serial console support were disabled, the code could trivially be fixed to compile without errors.
2.6.21 has just opened so now is an excellent time to submit all the
remaining driver bits.
> Can you revert the removal?
Sure, I can undo the deletion at any time. And to generalize that, while
I'm eager to remove code for which nobody has shown any interest this by
no means is a one way road.
Ralf
prev parent reply other threads:[~2007-02-06 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 10:35 [MIPS] Remove Basler Excite support Koeller, T.
2007-02-05 10:35 ` Koeller, T.
2007-02-06 11:03 ` Ralf Baechle [this message]
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=20070206110358.GA29286@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Thomas.Koeller@baslerweb.com \
--cc=linux-mips@linux-mips.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