From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
Vitaly Wool <vwool@ru.mvista.com>
Subject: Re: [PATCH/RFC] remove len/ooblen confusion in MTD/NAND code
Date: Wed, 01 Nov 2006 15:59:27 +0200 [thread overview]
Message-ID: <1162389567.7527.6.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0610311249420.25906@lnxricardw.se.axis.com>
On Tue, 2006-10-31 at 12:58 +0100, Ricard Wanderlof wrote:
> My only comment at this stage is a trivial one: many of the debug texts do
> not match the function they are placed in. Doesn't really have anything to
> do with the reason for the patch though, but makes for confusing debug
> output.
True. Feel free to send a patch :-)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-01 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 11:51 [PATCH/RFC] remove len/ooblen confusion in MTD/NAND code Vitaly Wool
2006-10-31 11:58 ` Ricard Wanderlof
2006-11-01 13:59 ` Artem Bityutskiy [this message]
2006-11-01 14:41 ` Artem Bityutskiy
2006-11-02 7:02 ` Vitaly Wool
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=1162389567.7527.6.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
--cc=vwool@ru.mvista.com \
/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