mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: atull@opensource.altera.com, jgunthorpe@obsidianresearch.com,
	hpa@zytor.com, monstr@monstr.eu, rdunlap@infradead.org,
	mark.rutland@arm.com, linux-doc@vger.kernel.org,
	rubini@gnudd.com, pantelis.antoniou@konsulko.com,
	s.trumtrar@pengutronix.de, devel@driverdev.osuosl.org,
	sameo@linux.intel.com, nico@linaro.org,
	ijc+devicetree@hellion.org.uk, kyle.teske@ni.com,
	grant.likely@linaro.org, davidb@codeaurora.org,
	linus.walleij@linaro.org, cesarb@cesarb.net,
	devicetree@vger.kernel.org, jason@lakedaemon.net,
	pawel.moll@arm.com, iws@ovro.caltech.edu, broonie@kernel.org,
	philip@balister.org, dinguyen@opensource.altera.com,
	pavel@denx.de, yvanderv@opensource.altera.com,
	linux-kernel@vger.kernel.org, balbi@ti.com,
	delicious.quinoa@gmail.com, robh+dt@kernel.org, rob@landley.net,
	galak@codeaurora.org, akpm@linux-foundation.org,
	davem@davemloft.net, m.chehab@samsung.com
Subject: Re: [PATCH v6 0/4] FPGA Manager Framework
Date: Fri, 19 Dec 2014 07:38:28 -0800	[thread overview]
Message-ID: <20141219153828.GA19077@kroah.com> (raw)
In-Reply-To: <5901b1791e1c4b09b72cb22c5eca68ca@BL2FFO11FD047.protection.gbl>

On Fri, Dec 19, 2014 at 03:20:59PM +0100, Michal Simek wrote:
> Hi Greg,
> 
> On 12/18/2014 11:29 PM, atull@opensource.altera.com wrote:
> > From: Alan Tull <atull@opensource.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

  reply	other threads:[~2014-12-19 15:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 22:29 atull
2014-12-18 22:29 ` [PATCH v6 1/4] doc: add bindings document for altera fpga manager atull
2014-12-18 22:29 ` [PATCH v6 2/4] fpga manager: add sysfs interface document atull
2014-12-18 22:29 ` [PATCH v6 3/4] staging: fpga manager: framework core atull
2014-12-19 14:08   ` Michal Simek
2014-12-18 22:29 ` [PATCH v6 4/4] staging: fpga manager: add driver for socfpga fpga manager atull
2014-12-19  8:55   ` Steffen Trumtrar
2014-12-19 14:05     ` Michal Simek
2014-12-19 15:07       ` Steffen Trumtrar
2014-12-19 15:55         ` atull
2014-12-19 16:15           ` Steffen Trumtrar
2014-12-19 14:20 ` [PATCH v6 0/4] FPGA Manager Framework Michal Simek
2014-12-19 15:38   ` Greg KH [this message]
2014-12-19 15:47     ` atull
2014-12-19 16:49       ` 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=20141219153828.GA19077@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=atull@opensource.altera.com \
    --cc=balbi@ti.com \
    --cc=broonie@kernel.org \
    --cc=cesarb@cesarb.net \
    --cc=davem@davemloft.net \
    --cc=davidb@codeaurora.org \
    --cc=delicious.quinoa@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@opensource.altera.com \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=hpa@zytor.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=iws@ovro.caltech.edu \
    --cc=jason@lakedaemon.net \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=kyle.teske@ni.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=nico@linaro.org \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=pavel@denx.de \
    --cc=pawel.moll@arm.com \
    --cc=philip@balister.org \
    --cc=rdunlap@infradead.org \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=rubini@gnudd.com \
    --cc=s.trumtrar@pengutronix.de \
    --cc=sameo@linux.intel.com \
    --cc=yvanderv@opensource.altera.com \
    /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

Powered by JetHome