linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Red Hat <alan@redhat.com>,
	James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] SCSI atp870u.c: make a needlessly global function static
Date: Mon, 15 Nov 2004 08:38:32 -0500	[thread overview]
Message-ID: <20041115133832.GC3964@devserv.devel.redhat.com> (raw)
In-Reply-To: <20041115015430.GF2249@stusta.de>

On Mon, Nov 15, 2004 at 02:54:30AM +0100, Adrian Bunk wrote:
> The patch below makes the function is870 which has no external users 
> static.

ACK. Makes total sense

      reply	other threads:[~2004-11-15 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  1:54 [2.6 patch] SCSI atp870u.c: make a needlessly global function static Adrian Bunk
2004-11-15 13:38 ` Alan Cox [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=20041115133832.GC3964@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).