linux-kernel - Re: [PATCH v6 0/4] FPGA Manager Framework

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: <20141219153828.GA19077@kroah.com>
Date:	Fri, 19 Dec 2014 07:38:28 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Michal Simek <michal.simek@...inx.com>
Cc:	atull@...nsource.altera.com, jgunthorpe@...idianresearch.com,
	hpa@...or.com, monstr@...str.eu, rdunlap@...radead.org,
	mark.rutland@....com, linux-doc@...r.kernel.org, rubini@...dd.com,
	pantelis.antoniou@...sulko.com, s.trumtrar@...gutronix.de,
	devel@...verdev.osuosl.org, sameo@...ux.intel.com, nico@...aro.org,
	ijc+devicetree@...lion.org.uk, kyle.teske@...com,
	grant.likely@...aro.org, davidb@...eaurora.org,
	linus.walleij@...aro.org, cesarb@...arb.net,
	devicetree@...r.kernel.org, jason@...edaemon.net,
	pawel.moll@....com, iws@...o.caltech.edu, broonie@...nel.org,
	philip@...ister.org, dinguyen@...nsource.altera.com, pavel@...x.de,
	yvanderv@...nsource.altera.com, linux-kernel@...r.kernel.org,
	balbi@...com, delicious.quinoa@...il.com, robh+dt@...nel.org,
	rob@...dley.net, galak@...eaurora.org, akpm@...ux-foundation.org,
	davem@...emloft.net, m.chehab@...sung.com
Subject: Re: [PATCH v6 0/4] FPGA Manager Framework

On Fri, Dec 19, 2014 at 03:20:59PM +0100, Michal Simek wrote:
> Hi Greg,
> 
> On 12/18/2014 11:29 PM, atull@...nsource.altera.com wrote:
> > From: Alan Tull <atull@...nsource.altera.com>
> > 
> > Dropping the changes to socfpga DTS and defconfig from this
> > patch set.
> > 
> > Kernel doc fixes and other minor fixes as listed in the patches.
> > 
> > Alan
> > 
> > Alan Tull (4):
> >   doc: add bindings document for altera fpga manager
> >   fpga manager: add sysfs interface document
> >   staging: fpga manager: framework core
> >   staging: fpga manager: add driver for socfpga fpga manager
> > 
> >  drivers/staging/Kconfig                            |    2 +
> >  drivers/staging/Makefile                           |    1 +
> >  .../Documentation/ABI/sysfs-class-fpga-manager     |   38 ++
> >  .../Documentation/bindings/altera-fpga-mgr.txt     |   17 +
> >  drivers/staging/fpga/Kconfig                       |   29 +
> >  drivers/staging/fpga/Makefile                      |    9 +
> >  drivers/staging/fpga/fpga-mgr.c                    |  551 ++++++++++++++++
> >  drivers/staging/fpga/socfpga.c                     |  694 ++++++++++++++++++++
> >  include/linux/fpga/fpga-mgr.h                      |  124 ++++
> >  9 files changed, 1465 insertions(+)
> >  create mode 100644 drivers/staging/fpga/Documentation/ABI/sysfs-class-fpga-manager
> >  create mode 100644 drivers/staging/fpga/Documentation/bindings/altera-fpga-mgr.txt
> >  create mode 100644 drivers/staging/fpga/Kconfig
> >  create mode 100644 drivers/staging/fpga/Makefile
> >  create mode 100644 drivers/staging/fpga/fpga-mgr.c
> >  create mode 100644 drivers/staging/fpga/socfpga.c
> >  create mode 100644 include/linux/fpga/fpga-mgr.h
> > 
> 
> I think we have reasonable number of patches which can go to the staging
> and we can work on it and extend it. I have xilinx zynq driver in my repository too.
> Also I would try to integrate staging/gs_fpgaboot/ because they do just the same
> thing. Also char/xilinx_hwicap should be added to this subfolder (and clean a lot).
> I am not aware about any other fpga driver in the tree but I didn't grep it
> (IRC xillybus targets a little bit different thing). Please let me know if you are
> aware about different one.
> 
> I was talking to Altera guys at ELCE and conclusion was that will be the best to
> maintain future drivers/fpga/ together.
> It means if there is no problem with this series. Do you want me to add these
> patches to any repository at kernel.org and send you pull request?
> Or you just prefer to take these patches directly to staging and we will use
> separate repository later?

We don't need a whole new repo just for a single driver or a few new
files, I'll take these after the new year (can't do anything until
3.19-rc1 is out, and then it is vacation time.)

So I'll just take them from patches, no need for a git tree at all.

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/