linux-kernel - Re: [GIT PULL] Staging driver patches for 3.15-rc1

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: <20140402200428.GE26966@kroah.com>
Date:	Wed, 2 Apr 2014 13:04:28 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Insop Song <insop.song@...nspeed.com>,
	devel@...uxdriverproject.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Staging driver patches for 3.15-rc1

On Wed, Apr 02, 2014 at 10:24:03AM +0200, Paul Bolle wrote:
> On Tue, 2014-04-01 at 11:48 -0700, Greg KH wrote:
> > Staging driver pull request for 3.15-rc1
> > 
> > Here's the huge drivers/staging/ update for 3.15-rc1.
> > 
> > Loads of cleanup fixes, a few drivers removed, and some new ones added.
> > 
> > All have been in linux-next for a while.
> >
> >[...]
> >
> > Insop Song (1):
> >       staging: fpgaboot: Xilinx FPGA firmware download driver
> 
> This commit adds checks for CONFIG_B4860G100. Is a patch to add a
> Kconfig symbol B4860G100 perhaps queued somewhere?

Insop, I thought this config option was coming from some other place,
right?

> It also adds this Makefile line:
>     ccflags-$(CONFIG_GS_FPGA_DEBUG)    := -DDEBUG
> 
> But there's no Kconfig symbol GS_FGPA_DEBUG. On the other hand, the code
> involved doesn't seem to use either DEBUG or dev_dbg() so perhaps it
> isn't actually needed. (But note that the code does check for
> DEBUG_FPGA, which apparently has to be set manually.)

Odds are we can just drop this, patches gladly accepted :)

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/