From: "Georg Nikodym" <georgn@somanetworks.com>
To: linux-mtd@lists.infradead.org
Subject: [Fwd: Re: 2.4.16-rmk1 patch file]
Date: 06 Dec 2001 11:33:08 -0500 [thread overview]
Message-ID: <1007656389.1783.18.camel@keller> (raw)
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
I sent the attached to the ARM kernel list because of a ^M the official
ARM architecture and Russell says that it's actually in the MTD CVS...
(I'm not on this list, so you'll need to Cc me on replies)
[-- Attachment #2: Forwarded message - Re: 2.4.16-rmk1 patch file --]
[-- Type: message/rfc822, Size: 1884 bytes --]
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Georg Nikodym <georgn@somanetworks.com>
Cc: linux-arm@lists.arm.linux.org.uk
Subject: Re: 2.4.16-rmk1 patch file
Date: Thu, 6 Dec 2001 16:17:55 +0000
Message-ID: <20011206161755.C11287@flint.arm.linux.org.uk>
On Thu, Dec 06, 2001 at 10:56:21AM -0500, Georg Nikodym wrote:
> In the "One of lifes minor irritations" department, patch-2.4.16-rmk1
> contains the following useless change:
>
> diff -urN orig/fs/jffs2/erase.c linux/fs/jffs2/erase.c
> --- orig/fs/jffs2/erase.c Sun Oct 14 20:53:27 2001
> +++ linux/fs/jffs2/erase.c Thu Nov 1 20:36:07 2001
> @@ -215,7 +215,7 @@
>
> D2({
> int i=0;
> - struct jffs2_raw_node_ref *this;
> + struct jffs2_raw_node_ref *this; ^M
> printk(KERN_DEBUG "After remove_node_refs_from_ino_list: \n"
> KERN_DEBUG
> );
>
> (The control-m is real in the actual patch).
>
> Can this diff be removed, please?
Please ask on the MTD list - the ^M appears to be in the MTD CVS.
next reply other threads:[~2001-12-06 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 16:33 Georg Nikodym [this message]
2001-12-06 16:48 ` [Fwd: Re: 2.4.16-rmk1 patch file] David Woodhouse
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=1007656389.1783.18.camel@keller \
--to=georgn@somanetworks.com \
--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.