linux-kernel - Re: [git patches] libata fixes

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: <alpine.LFD.2.00.0901270748290.3123@localhost.localdomain>
Date:	Tue, 27 Jan 2009 07:50:23 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jeff Garzik <jeff@...zik.org>, Tejun Heo <tj@...nel.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git patches] libata fixes



On Tue, 27 Jan 2009, Jeff Garzik wrote:
> 
> Please pull from 'upstream-linus' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git upstream-linus
> 
> to receive the following updates:
> 
>  drivers/ata/Kconfig              |    6 ++--
>  drivers/ata/libata-sff.c         |   12 ++++++-
>  drivers/ata/pata_rb532_cf.c      |    2 -
>  drivers/ata/pata_via.c           |   22 +++++++++---
>  drivers/ata/sata_mv.c            |   56 ++++++++++++++----------------
>  drivers/ata/sata_nv.c            |   70 +++++++++++++++++++++++--------------
>  include/linux/pci_ids.h          |    4 ++
>  7 files changed, 104 insertions(+), 68 deletions(-)
>  delete mode 100644 arch/arm/mach-integrator/clock.h

Hmm. That delete of the empty file is "correct" (and probably came as a 
result of somebody doing "make distclean" which deletes empty files), but 
should not have been committed as part of "libata-sff: fix incorrect EH 
message".

Seems to be a mistake, and a small one, but still.. Be more careful.

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