All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jes@wildopensource.com
Cc: adam@yggdrasil.com, linux-acenic@sunsite.dk,
	linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.3-pre4/drivers/acenic.c: pci_unmap_addr_set not defined for x86
Date: Thu, 24 Jan 2002 06:16:05 -0800 (PST)	[thread overview]
Message-ID: <20020124.061605.131916581.davem@redhat.com> (raw)
In-Reply-To: <15440.5902.755260.764642@trained-monkey.org>
In-Reply-To: <15440.4044.565375.681853@trained-monkey.org> <20020124.054626.15688749.davem@redhat.com> <15440.5902.755260.764642@trained-monkey.org>

   From: Jes Sorensen <jes@wildopensource.com>
   Date: Thu, 24 Jan 2002 09:15:42 -0500
   
   Considering a) it's just a few keystrokes to add a CC: line, b) it's the
   driver authors who are the first to get the bug reports, then yes it
   seems like a very reasonable request.

This list actually is the first place the reports typically
go to.

I'm a responsible maintainer, when I add a problem, I always go back
and fix it or revert my changes.  I never disappear after making
these kinds of changes.

  reply	other threads:[~2002-01-24 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24 10:01 linux-2.5.3-pre4/drivers/acenic.c: pci_unmap_addr_set not defined for x86 Adam J. Richter
2002-01-24 13:36 ` David S. Miller
2002-01-24 15:41   ` Narayan Desai
2002-01-24 15:42     ` David S. Miller
2002-01-24 13:44 ` Jes Sorensen
2002-01-24 13:46   ` David S. Miller
2002-01-24 14:15     ` Jes Sorensen
2002-01-24 14:16       ` David S. Miller [this message]
2002-01-24 14:43         ` Jes Sorensen

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=20020124.061605.131916581.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=adam@yggdrasil.com \
    --cc=jes@wildopensource.com \
    --cc=linux-acenic@sunsite.dk \
    --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.