linux-kernel - bfsort whitelist patch apparently applied twice

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-next>] [day] [month] [year] [list]

Date:	Mon, 07 Jul 2008 10:35:02 -0400
From:	Tony Camuso <tcamuso@...hat.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
CC:	"Schoeller, Patrick (Linux - Houston, TX)" <Patrick.Schoeller@...com>
Subject: bfsort whitelist patch apparently applied twice

In the most recent pull from Linus' tree, I see that the patch
I submitted on 14-May-2008 was merged twice in the git log.

  commits: a16b4bcd31a73a81b6d2b8ffa6b5f6ed01cf6d64
      and: a1676072558854b95336c8f7db76b0504e909a0a

The result is that now the DL360 and DL380 are whitelisted twice
and the DL385 G2 and DL585 G2 are not whitelisted at all!

Can one of these redundant commits be backed out?

Thanks and regards,
Tony

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