From: Andrew Morton <akpm@osdl.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
bunk@stusta.de
Subject: Re: [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers
Date: Sat, 7 Jan 2006 17:45:23 -0800 [thread overview]
Message-ID: <20060107174523.460f1849.akpm@osdl.org> (raw)
In-Reply-To: <1136680734.30348.34.camel@pmac.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
>
> > > 2. What was the reason for marking them obsolete?
> >
> > The changelog says:
> > - David Woodhouse: large MTD and JFFS[2] update
>
> I didn't ask who; I knew that. I asked you _why_. Admittedly, I happen
> to know that too - but I want to know if _you_ know it.
>
> Since you've taken it upon yourself to decide the timescale of the
> removal, surely it's reasonable to expect that you do actually know what
> you're removing and why it's obsolescent?
>
Hey, Adrian isn't an MTD developer - give him a break.
What he's doing here is to poke other maintainers into getting the tree
cleaned up. It's a useful thing to do.
If you, an MTD maintainer, can tell him what we _should_ be doing, I'm sure
Adrian would help.
next prev parent reply other threads:[~2006-01-08 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 22:07 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
2006-01-08 0:00 ` David Woodhouse
2006-01-08 0:24 ` Adrian Bunk
2006-01-08 0:38 ` David Woodhouse
2006-01-08 1:45 ` Andrew Morton [this message]
2006-01-08 12:41 ` David Woodhouse
2006-01-08 12:57 ` Adrian Bunk
2006-01-08 13:06 ` David Woodhouse
2006-01-08 14:14 ` [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN Adrian Bunk
2006-01-08 14:24 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 18:14 [2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers Adrian Bunk
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=20060107174523.460f1849.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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