public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: sfr@canb.auug.org.au
Cc: jgrimm2@us.ibm.com, linux-kernel@vger.kernel.org,
	trivial@rustcorp.com.au
Subject: Re: [PATCH] warning and unused in sctp.h
Date: Mon, 24 Mar 2003 22:46:27 -0800 (PST)	[thread overview]
Message-ID: <20030324.224627.70037101.davem@redhat.com> (raw)
In-Reply-To: <20030325142400.194987b0.sfr@canb.auug.org.au>

   From: Stephen Rothwell <sfr@canb.auug.org.au>
   Date: Tue, 25 Mar 2003 14:24:00 +1100
   
   This patch changes a flags argument to spin_lock_irq_save to unsigned long
   and removes its unused attribute.  The first gets rid of several warnings
   and the second is "obviously correct" (at least according to Rusty) :-).
   
Applied, thank you.

   Thanks to DaveM for forcing me to build kernels with a 64 cross compiler :-)

No problem. :)

  reply	other threads:[~2003-03-25  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  3:24 [PATCH] warning and unused in sctp.h Stephen Rothwell
2003-03-25  6:46 ` David S. Miller [this message]
2003-03-25 15:00 ` Jon Grimm

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=20030324.224627.70037101.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jgrimm2@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=trivial@rustcorp.com.au \
    /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