From: Martin Mares <mj@ucw.cz>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] pciutils/linux: Support for the HyperTransport capability
Date: Fri, 28 May 2004 13:40:17 +0200 [thread overview]
Message-ID: <20040528114017.GA3708@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.55.0404201720290.28193@jurand.ds.pg.gda.pl>
Hello!
> Here's a patch for initial support for the HyperTransport capability for
> pciutils. I've developed full dumping code for the sub-capabilities I was
> able to test (plus for the Revision ID one, for it being so trivial) with
> my hardware. Others are reported by their names only, without any details
> -- for a few of them it's probably most we can do anyway.
I've applied it, but I tried to simplify the code, because it seemed
unnecessarily hairy to me. I hope I didn't break anything.
I'll release 2.1.99-test4 in a hour, so please check it once again.
> The changes for lib/header.h are probably applicable to <linux/pci.h> as
> well -- they apply cleanly to 2.4, but require a manual intervention for
> 2.6 due to context changes. I'll rediff if this patch is accepted for
> Linux.
I would vote for keeping it in pciutils and copying it to <linux/pci.h>
when it will be needed by any kernel drivers.
Have a nice fortnight
--
Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
Anything is good and useful if it's made of chocolate.
next prev parent reply other threads:[~2004-05-28 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 15:58 [patch] pciutils/linux: Support for the HyperTransport capability Maciej W. Rozycki
2004-05-28 11:40 ` Martin Mares [this message]
2004-05-31 10:51 ` Maciej W. Rozycki
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=20040528114017.GA3708@ucw.cz \
--to=mj@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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