linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Mareš" <mj@ucw.cz>
To: Linux-PCI Mailing List <linux-pci@vger.kernel.org>
Subject: Released pciutils-3.6.3
Date: Wed, 22 Jan 2020 11:54:01 +0100	[thread overview]
Message-ID: <mj+md-20200122.105243.53346.albireo@ucw.cz> (raw)

Hello, world!\n

After a long hibernation, I just released pciutils-3.6.3.

At the moment, my patch queue is empty, so if you sent me a patch
over last few months and you did have not received a reply, please
re-send it.

From the changelog:

	* `lspci -t' (tree mode) can be combined with `-s' to show a sub-tree.
	  We also fixed potential buffer overflows in the tree dumper.

	* Cleaned messy code for dumping of I/O, memory, and ROM regions.
	  This helped fixing a bug, which caused some 64-bit regions to be
	  reported as virtual. All flags are now printed after the address
	  (previously, "[virtual]" and "[enhanced]" were before it for no good
	  reason).

	* Added pci_find_cap_nr() to the library, which handles capabilities
	  which occur multiple times in a single device.

	* Minor improvements in printing of PCIe capabilities.

	* We now decode the Multicast and Secondary PCI Express extended
	  capabilities.

	* The list of capability names available to setpci was updated.

	* Minor bugs were fixed in FreeBSD and Solaris ports.

	* We now prefer HTTPS URLs in all documentation

	* The pci.ids file has a man page.

	* As usually, updated pci.ids to the current snapshot of the database.

				Have a nice fortnight
-- 
Martin `MJ' Mareš                        <mj@ucw.cz>   http://mj.ucw.cz/
United Computer Wizards, Prague, Czech Republic, Europe, Earth, Universe
"I don't give a damn for a man that can only spell a word one way." -- M. Twain

                 reply	other threads:[~2020-01-22 10:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=mj+md-20200122.105243.53346.albireo@ucw.cz \
    --to=mj@ucw.cz \
    --cc=linux-pci@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).