From: Thomas Gleixner <tglx@linutronix.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/mtd/devices/: remove dead _ecc code
Date: Wed, 28 Jun 2006 09:16:25 +0200 [thread overview]
Message-ID: <1151478985.25491.489.camel@localhost.localdomain> (raw)
In-Reply-To: <20060627131116.GL23314@stusta.de>
On Tue, 2006-06-27 at 15:11 +0200, Adrian Bunk wrote:
> nand_ecc isn't dead code.
>
> But if I do understand correctly, you have pending patches to let the
> code your patch made dead code and my patch would have removed be used
> again?
Ooops, sorry for shooting too fast. You're right I rendered that stuff
dead unintentionally. But removing is not an option. I fix it proper
Thanks
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/mtd/devices/: remove dead _ecc code
Date: Wed, 28 Jun 2006 09:16:25 +0200 [thread overview]
Message-ID: <1151478985.25491.489.camel@localhost.localdomain> (raw)
In-Reply-To: <20060627131116.GL23314@stusta.de>
On Tue, 2006-06-27 at 15:11 +0200, Adrian Bunk wrote:
> nand_ecc isn't dead code.
>
> But if I do understand correctly, you have pending patches to let the
> code your patch made dead code and my patch would have removed be used
> again?
Ooops, sorry for shooting too fast. You're right I rendered that stuff
dead unintentionally. But removing is not an option. I fix it proper
Thanks
tglx
next prev parent reply other threads:[~2006-06-28 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 21:58 [2.6 patch] drivers/mtd/devices/: remove dead _ecc code Adrian Bunk
2006-06-21 22:24 ` Thomas Gleixner
2006-06-21 22:24 ` Thomas Gleixner
2006-06-27 13:11 ` Adrian Bunk
2006-06-27 13:11 ` Adrian Bunk
2006-06-28 7:16 ` Thomas Gleixner [this message]
2006-06-28 7:16 ` Thomas Gleixner
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=1151478985.25491.489.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--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 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.