public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Insop Song <Insop.Song@gainspeed.com>,
	Paul Bolle <pebolle@tiscali.nl>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"'insop.song@gmail.com'" <insop.song@gmail.com>
Subject: Re: [GIT PULL] Staging driver patches for 3.15-rc1
Date: Fri, 04 Apr 2014 07:16:24 +0200	[thread overview]
Message-ID: <533E4028.7040505@monstr.eu> (raw)
In-Reply-To: <20140402230837.GA24324@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]

On 04/03/2014 01:08 AM, Greg KH wrote:
> On Wed, Apr 02, 2014 at 08:52:18PM +0000, Insop Song wrote:
>> On Wed, April 02, 2014 1:04 PM, Greg KH wrote:
>>> 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?
>>>
>>
>> Paul,
>> I didn't include CONFIG_B4860G100 in Kconfig in original patch set,
>> since programming FPGA method can vary in different system, and this
>> was discussed during the review with Greg as well.
>>
>> However, actual fpga programming method is well contained in io.c with
>> ifdef-ed CONFIG_B4860G100, now I think I might better to update
>> Kconfig to include CONFIG_B4860G100.
>>
>> Greg, what do you think? Any harm to add custom board CONFIG* to
>> staging Kconfig? Let me know.
> 
> Let's see what it would look like and we can go from there.

That's interesting driver. Maybe good time to refresh my work
around fpga manager.
http://permalink.gmane.org/gmane.linux.kernel/1573330

It is the framework which just provides what you have done there.

I need to finish some work and let me look at it next week.
It should be easy for you to switch to it.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-04-04  5:16 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
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 [this message]
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=533E4028.7040505@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=Insop.Song@gainspeed.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=insop.song@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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