linux-kernel - Re: [GIT PULL] MMC updates for 2.6.26

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

Message-Id: <1216296279.22564.8.camel@violet.holtmann.net>
Date:	Thu, 17 Jul 2008 14:04:39 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] MMC updates for 2.6.26

Hi Pierre,

> > >  45 files changed, 6054 insertions(+), 1320 deletions(-)
> > 
> > If you had done the "--summary", you'd also have seen these bogus:
> > 
> > 	 mode change 100644 => 100755 drivers/mmc/core/sdio_io.c
> > 	 mode change 100644 => 100755 include/linux/mmc/sdio_func.h
> > 
> > entries.
> > 
> > I have no idea why you think those things should be executable, but it 
> > happened in commit 6d37333163025b46afbcad434ec9a5f2e88e7254 ("mmc: fix 
> > sdio_io sparse errors").
> > 
> 
> Ouch. It was in the patch submitted to me, but I overlooked the mode
> changes there. I wasn't fully aware git could express such things in
> the patches. :)

I NAKed these patches and Tomas re-sent them, but it seems you picked
the wrong ones from the mailing list.

This mess always happens if a FAT filesystem is involved somehow :(

Regards

Marcel


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