All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH resent] arch/ia64/sn: use seq_file in sn_proc_fs.c
Date: Wed, 08 Sep 2004 17:25:06 +0000	[thread overview]
Message-ID: <20040908102506.331abb02.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0409031150050.4971-100000@woolami.melbourne.sgi.com>

On Mon, 6 Sep 2004 14:48:44 +1000 (EST) Mark Goodwin wrote:

| On Fri, 3 Sep 2004, Randy.Dunlap wrote:
| 
| > On Fri, 3 Sep 2004 12:05:49 +1000 (EST) Mark Goodwin wrote:
| > | ---
| > | 
| > | --- 2.6.8-rc2/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	Tue Aug 17 11:45:18 2004
| > | +++ 2.6.8-rc2-seq_file/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	Wed Aug 18 07:22:24 2004
| > 
| > Hi-
| > This no longer applies cleanly to current tree (2.6.9-rc1 or -mm3).
| 
| ok, I've redone the patch against 2.6.9-rc1 (actually top-of-tree bk),
| see below.
| 
| > Please use tabs instead of spaces...
| 
| ok
| 
| > Have you run any of this thru sparse?
| 
| No I hadn't, but have now. Using sparse from 
| http://www.codemonkey.org.uk/projects/bitkeeper/sparse/sparse-2004-09-05.tar.gz
| 
| It complains about all sorts of stuff in headers I'm including, but
| apparently no complaints in sn_proc_fs.c itself.
| 
| > It may be clean as is, but I thought that I saw a couple of
| > questionable items in it.
| > 
| Thanks for the review .. which items were questionable? Here's the revised
| patch for your consideration.

I don't recall, but I would trust sparse more than my eyes,
so don't worry about them.  I don't see any questionable bits now.

Thanks for the update.

--
~Randy

      parent reply	other threads:[~2004-09-08 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03  2:05 [PATCH resent] arch/ia64/sn: use seq_file in sn_proc_fs.c Mark Goodwin
2004-09-03 22:02 ` Randy.Dunlap
2004-09-06  4:48 ` Mark Goodwin
2004-09-08 17:25 ` Randy.Dunlap [this message]

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=20040908102506.331abb02.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-ia64@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.