From: Paul Bolle <pebolle@tiscali.nl>
To: Greg KH <gregkh@linuxfoundation.org>,
Insop Song <insop.song@gainspeed.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PULL] Staging driver patches for 3.15-rc1
Date: Wed, 02 Apr 2014 10:24:03 +0200 [thread overview]
Message-ID: <1396427043.18431.20.camel@x220> (raw)
In-Reply-To: <20140401184817.GA21855@kroah.com>
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?
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.)
Paul Bolle
next prev parent reply other threads:[~2014-04-02 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:48 [GIT PULL] Staging driver patches for 3.15-rc1 Greg KH
2014-04-02 8:24 ` Paul Bolle [this message]
2014-04-02 20:04 ` Greg KH
2014-04-02 20:52 ` Insop Song
2014-04-02 23:08 ` Greg KH
2014-04-04 5:16 ` Michal Simek
2014-09-04 23:13 ` Paul Bolle
2014-09-04 23:21 ` Greg KH
2014-09-05 11:28 ` [PATCH] [next-20140904] staging: gs_fpgaboot: remove checks for CONFIG_B4860G100 Paul Bolle
2014-04-03 8:32 ` [PATCH] staging: fpgaboot: clean up Makefile Paul Bolle
2014-04-03 17:14 ` Insop Song
2014-04-03 17:56 ` Dan Carpenter
2014-04-02 13:06 ` [GIT PULL] Staging driver patches for 3.15-rc1 Shuah Khan
2014-04-02 20:03 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1396427043.18431.20.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=insop.song@gainspeed.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox