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]
Date:	Thu, 12 May 2011 13:54:46 +0200
From:	Par-Gunnar HJALMDAHL <par-gunnar.p.hjalmdahl@...ricsson.com>
To:	Greg KH <greg@...ah.com>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
	Pavan Savoy <pavan_savoy@...y.com>,
	Vitaly Wool <vitalywool@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Arnd Bergmann <arnd@...db.de>,
	Marcel Holtmann <marcel@...tmann.org>,
	Lukasz Rymanowski <Lukasz.Rymanowski@...to.com>,
	Linus WALLEIJ <linus.walleij@...ricsson.com>,
	Par-Gunnar Hjalmdahl <pghatwork@...il.com>,
	Lee Jones <lee.jones@...aro.org>,
	Mathieu Poirier <mathieu.poirier@...aro.org>
Subject: RE: [PATCH v6] staging: Add ST-Ericsson CG2900 driver

> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: den 11 maj 2011 15:49
>
> > I used next-20110510 and in that tag the file
> include/Linux/mfd/core.h
> > The struct mfd_cell has a parameter called platform_data, while in
> your
> > build it seems it doesn't.
> > This was changed very recently in the core.h file (on April 6).
> > So for core.h the last commit ID I have in the tag I built upon is
> > 558aa9c0d620b91a896d5e39ce8a570bed65589b.
> 
> So do I need that patch on the staging-next tree also?
> 
> Or is it an issue of building this on x86-64...
> 
> thanks,
> 
> greg k-h

Hi Greg,

I downloaded you staging tree and compared the logs for the core.h file.
Compared to linux-next tag next-20110510 it is missing 2 commits:
4dbee6b76fffd5740e87e286f4f4c1c15901bcae
558aa9c0d620b91a896d5e39ce8a570bed65589b
where the first one is the "oldest" one in the log and is the most
important one for my patch.
Another option would be for me to fix the patch for your tree, but
then I would probably have to fix it back in a few days when you update
your staging tree to Linux-next. How often is your tree updated?

The easiest is probably to wait a few days until you have the next-20110510
tag in your tree and then apply the patch.

Thanks,
P-G

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ