linux-kernel - Re: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR

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: <20080730034255.ac5aa6c2.akpm@linux-foundation.org>
Date:	Wed, 30 Jul 2008 03:42:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	mcs6502@...il.com
Cc:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs
 within VENDOR_IDs

On Wed, 30 Jul 2008 18:50:50 +1000 mcs6502@...il.com wrote:

> From: mcs6502@...il.com
> To: unlisted-recipients:;;@imap1.linux-foundation.org (no To-header on input)

Something went wrong with the From: and To: lines.

Jesse wasn't cc'ed?

> Subject: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR_IDs

a) the patch title shouldn't include the kernel version - that
   information becomes instantly irrelevant (and soon wrong) as soon as
   someone merges the patch.

   It is sometimes useful to include this information, but it should
   be inside [], so the patch recipient can automatically remove it.

   (otoh, the patch _should_ be against latest Linus mainline, so
   it's not very useful info).

b) all 31 patches had the same title.  This causes numerous
   problems.  Please think up unique and relevant titles for each
   patch.

> Date: 	Wed, 30 Jul 2008 18:50:50 +1000
> Sender: linux-kernel-owner@...r.kernel.org
> 
> The following 31 patches attempt to bring pci_ids.h back into order.

This patchset will be utterly ghastly for someone to maintain for two
months.  The PCI and linux-next trees will be worst hit.

So we either

a) slam it into mainline immediately or

b) ask you to regenerate it during the 2.6.28 merge window or

c) forget the whole idea.

--
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/