lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200808251615.24785.bjorn.helgaas@hp.com>
Date:	Mon, 25 Aug 2008 16:15:24 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] use lspci style for [%04x:%04x] vendor/device

On Monday 25 August 2008 04:05:25 pm Arjan van de Ven wrote:
> On Mon, 25 Aug 2008 16:01:38 -0600
> Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> 
> > These patches change various debug messages to use "[%04x:%04x]" for
> > PCI vendor/device IDs to follow the format used by lspci(8).
> 
> I hope you're adding a new whicked special format specifier for this
> ... taking a PCI dev struct as argument.
> 
> That's be really nice to have;-)

Huh, that's kind of a cool idea.  The %p<x> namespace is unlimited,
right?  If it were only a single character specifier, this one doesn't
seem common enough to eat 1/26 of the space.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ