From: Jeff Garzik <jgarzik@pobox.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: mj@ucw.cz, linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: PCI devices with no PCI_CACHE_LINE_SIZE implemented
Date: Thu, 06 May 2004 11:45:42 -0400 [thread overview]
Message-ID: <409A5DA6.4020801@pobox.com> (raw)
In-Reply-To: <20040506132810.GB13482@lists.us.dell.com>
Matt Domsch wrote:
> Martin, below is a patch to lower the severity of this printk to
> KERN_DEBUG, as there are devices which (properly) don't implement the
> PCI_CACHE_LINE_SIZE register, and it's not a bug, so don't print at a
> WARNING level.
>
> Thanks,
> Matt
I'd send it straight to Marcelo, saying that the 2.6 PCI maintainer
approved it.... Martin hasn't hacked on kernel code in a while...
Jeff
next prev parent reply other threads:[~2004-05-06 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 13:28 PCI devices with no PCI_CACHE_LINE_SIZE implemented Matt Domsch
2004-05-06 15:45 ` Jeff Garzik [this message]
2004-05-10 10:49 ` Martin Mares
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 19:53 Matt Domsch
2004-05-05 22:31 ` Greg KH
2004-05-05 22:48 ` Matt Domsch
2004-05-05 23:42 ` Greg KH
2004-05-05 22:50 ` Matt Domsch
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=409A5DA6.4020801@pobox.com \
--to=jgarzik@pobox.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mj@ucw.cz \
/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