public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Chris Kohn <ckohn@xilinx.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Jason Wu <huanyu@xilinx.com>
Subject: Re: [PATCH] staging: Add Xilinx Clocking Wizard driver
Date: Wed, 1 Oct 2014 10:57:04 -0700	[thread overview]
Message-ID: <20141001175704.GA9625@kroah.com> (raw)
In-Reply-To: <e6907682-8d66-4df0-9a9e-a1079933e358@BL2FFO11FD008.protection.gbl>

On Wed, Oct 01, 2014 at 10:46:16AM -0700, Sören Brinkmann wrote:
> On Wed, 2014-10-01 at 10:39AM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Oct 01, 2014 at 10:21:48AM -0700, Soren Brinkmann wrote:
> > > Add a driver for the Xilinx Clocking Wizard soft IP. The clocking wizard
> > > provides an AXI interface to dynamically reconfigure the clocking
> > > resources of Xilinx FPGAs.
> > 
> > Why not just do the few things you have on the TODO list and get it
> > merged to the "proper" part of the kernel, keeping it out of the staging
> > tree?
> 
> The few things are not that easy and as I mention in the TODO file,
> there are some patches on LKML that would greatly simplify this
> driver/reduce the need for code duplication.
> I thought this is a good way to wait for those parts to mature while
> people could already use the driver as passive part in their clock tree.

Ok, fair enough, as long as you keep working on the driver to get it out
of staging, I don't have an objection to it.  I'll go queue it up later
today.

greg k-h

  reply	other threads:[~2014-10-01 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 17:21 [PATCH] staging: Add Xilinx Clocking Wizard driver Soren Brinkmann
2014-10-01 17:39 ` Greg Kroah-Hartman
2014-10-01 17:46   ` Sören Brinkmann
2014-10-01 17:57     ` Greg Kroah-Hartman [this message]
2014-10-01 18:04       ` Sören Brinkmann
2014-10-01 18:58 ` Dan Carpenter
2014-10-01 19:04   ` Sören Brinkmann
2014-10-01 21:02   ` [PATCH v2] " Soren Brinkmann
2014-10-01 23:19     ` Laurent Pinchart
2014-10-02  2:33       ` Sören Brinkmann

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=20141001175704.GA9625@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ckohn@xilinx.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=huanyu@xilinx.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.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