public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: "David S. Miller" <davem@redhat.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 09:43:36 -0500	[thread overview]
Message-ID: <15440.7576.636899.378071@trained-monkey.org> (raw)
In-Reply-To: <20020124.061605.131916581.davem@redhat.com>
In-Reply-To: <15440.4044.565375.681853@trained-monkey.org> <20020124.054626.15688749.davem@redhat.com> <15440.5902.755260.764642@trained-monkey.org> <20020124.061605.131916581.davem@redhat.com>

>>>>> "David" == David S Miller <davem@redhat.com> writes:

David>    From: Jes Sorensen <jes@wildopensource.com> Date: Thu, 24 Jan
David> 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.

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

Actually thats not the case in my experience, very often thing like that
go to the driver specific mailing lists or the driver maintainer in
private email. In fact this more common than a report going
linux-kernel.

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

I never claimed you don't, but some reports you never receive.

All I am suggesting is a CC, no fairytales or other stories to go with
it that actually takes time to write.

Jes

      reply	other threads:[~2002-01-24 14:44 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
2002-01-24 14:43         ` Jes Sorensen [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=15440.7576.636899.378071@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=adam@yggdrasil.com \
    --cc=davem@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox