From: "Michael S. Zick" <mszick@wolfbutter.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: prezeroing patch test against 2.6.11-rc2-pa0
Date: Sun, 23 Jan 2005 08:36:25 -0600 [thread overview]
Message-ID: <200501230836.26024.mszick@wolfbutter.com> (raw)
In-Reply-To: <41F2E78B.5070908@tiscali.be>
On Sat January 22 2005 17:53, Joel Soete wrote:
> Just an update to mentioned that the last Christoph's patch against our 2.6.11-rc2-pa0 (with some small ack) boot fine on my c110:
> # ps -ef | grep scr
> root 10 1 0 00:38 ? 00:00:04 [kscrubd0]
> :-)
>
Joel,
That sounds good. I haven't been watching for newer patches.
I have been working on my patch de-mangler.
It has been slow going because I have never used Lua before.
I have had it on my to-do list of things to learn for several years.
I started out just to correct indentation whitespace...
Now it also reformats bad hunk headers
and re-writes incorrect hunk headers.
Both with informative messages to the user. None of that:
"Malformed patch" and exit.
Which is what the patch program does.
I have a couple more small changes to make, but it is working
pretty well now.
Given a 643,000+ line patchfile (21 Mbyte) it takes about
10 seconds to re-write it.
With a reasonable sized patchfile, you can't even notice
it's run time.
So it has been fun, even if we don't need it for Christoph's
old patchfiles.
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2005-01-23 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41DE941B00001965@mail-6-bnl.tiscali.it>
[not found] ` <41F2E78B.5070908@tiscali.be>
2005-01-23 14:36 ` Michael S. Zick [this message]
2005-01-24 16:34 ` prezeroing patch test against 2.6.11-rc2-pa0 [Was: copy_user_page_asm suggested 64bit improvment [Was: [parisc-linux] clear user page test]] Christoph Lameter
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=200501230836.26024.mszick@wolfbutter.com \
--to=mszick@wolfbutter.com \
--cc=parisc-linux@lists.parisc-linux.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