linux-kernel - Re: [PATCH] West Bridge Astoria Driver 2.6.35

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: <20100831163220.GA6440@kroah.com>
Date:	Tue, 31 Aug 2010 09:32:20 -0700
From:	Greg KH <greg@...ah.com>
To:	David Cross <david.cross@...ress.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] West Bridge Astoria Driver 2.6.35

On Tue, Aug 31, 2010 at 09:17:18AM -0700, David Cross wrote:
> 
> > I get a build error when I try to build this driver:
> >
> drivers/staging/westbridge/astoria/block/../include/linux/westbridge/c>
> yasmisc.h:521:2: error: expected declaration specifiers or '...' before  >
> 'cy_as_hal_device_tag'
> 
> > It looks like the #include mess isn't working quite properly.
> 
> > Also note that this driver is building on an x86-64 platform, which is
> > something that you probably don't want :)
> 
> > So, for now, I'll just mark the driver as CONFIG_BROKEN and can you send
> > me some Kconfig patches against the next linux-next release which should
> > have this driver in it, so that it will build properly?
> 
> Sure, I can do that. I have since changed the Kconfig structure a bit. It
> actually will build properly with the correct .config as it is though. I can
> send you the .config if you would like.

It's up to the Kconfig rules to ensure that there can never be a
"non-correct" .config file, so that needs to be fixed so that the build
will never be broken no matter what type of options are selected.

Care to send a patch for that?

thanks,

greg k-h
--
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/