All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/10] 2.6.0-t3: struct C99 initialiser conversion
Date: Tue, 19 Aug 2003 16:30:51 +1000	[thread overview]
Message-ID: <20030819063050.GA17577@zip.com.au> (raw)

Hmmm... looks like 130k is too big for lk so I'll resend all split up.

----- Forwarded message from CaT <cat@zip.com.au> -----

Date: Tue, 19 Aug 2003 15:10:55 +1000
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitor-discuss@lists.sf.net
Subject: [PATCH] 2.6.0-t3: struct C99 initialiser conversion
Organisation: Furball Inc.

Ok. I think I did it.

I used grep+sed at first and then went through the resulting patches,
fixing any problems by hand until I could spot no more. It was a lot
of fun weeding out the mistakenly changed bit-definitions but I think
I got them all. I also compiled the kernel with make allyesconfig, 
checking into compile failure for anything I broke. Obviously though,
the more people that check this the better.

Also, while I finally decided on a single patch, I can split if
need be. It's 100k and not that hard to go through, esp with syntax
highlighting (I should know... I went through it several times :)

Anyhow... here goes...

----- End forwarded message -----

-- 
"How can I not love the Americans? They helped me with a flat tire the
other day," he said.
	- http://tinyurl.com/h6fo

             reply	other threads:[~2003-08-19  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  6:30 CaT [this message]
2003-08-19 14:48 ` [PATCH 0/10] 2.6.0-t3: struct C99 initialiser conversion Sam Ravnborg

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=20030819063050.GA17577@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.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.