All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jose Rivera <German.Rivera@freescale.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stuart Yoder <stuart.yoder@freescale.com>,
	Sharma Bhupesh <bhupesh.sharma@freescale.com>,
	"agraf@suse.de" <agraf@suse.de>,
	Hamciuc Bogdan <bhamciu1@freescale.com>,
	Erez Nir <nir.erez@freescale.com>,
	Katz Itai <itai.katz@freescale.com>,
	Scott Wood <scottwood@freescale.com>,
	Marginean Alexandru <R89243@freescale.com>,
	"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	Richard Schmitt <richard.schmitt@freescale.com>
Subject: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver
Date: Thu, 18 Jun 2015 16:02:57 -0700	[thread overview]
Message-ID: <20150618230257.GC32238@kroah.com> (raw)
In-Reply-To: <DM2PR0301MB1309D431C3972F3B696D0B56FEA50@DM2PR0301MB1309.namprd03.prod.outlook.com>

On Thu, Jun 18, 2015 at 03:01:22PM +0000, Jose Rivera wrote:
> Greg, 
> 
> Thanks for your feedback. It is our fault that we did not articulate
> clearly our intent with this patch series. First, for reference, let
> us summarize here the patches in question:
> 
> Patch 1: MC bus IRQ support
> Patch 2: add device binding path 'driver_override'
> Patch 3: Propagate driver_override for a child DPRC's children
> Patch 4: Upgraded MC bus driver to match MC fw 7.0.0
> Patch 5: Allow the MC bus driver to run without GIC support
> Patch 6: Add locking to serialize mc_send_command() calls
> Patch 7: Use DPMCP IRQ and completion var to wait for MC
> 
> With the exception of patches 2 and 3 (needed for vfio), our intent with
> the rest was to make to changes to work towards completing the "Add at
> least one device driver for a DPAA2 object" on the TODO list.

ah, missed that item, my fault.

> Before sending further patches we will submit an update to the TODO list
> to provide more detail and visibility into our plan to complete the
> "Add at least one device driver..." item.  It's too broad as written. 
> In particular, we think interrupt support is required and a pre-requisite.

Ok, that sounds good, please do.

thanks,

greg k-h

      reply	other threads:[~2015-06-18 23:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 21:59 [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver J. German Rivera
2015-06-09 21:59 ` [PATCH v4 1/7] staging: fsl-mc: MC bus IRQ support J. German Rivera
2015-06-09 21:59 ` [PATCH v4 2/7] staging: fsl_-mc: add device binding path 'driver_override' J. German Rivera
2015-06-09 21:59 ` [PATCH v4 3/7] staging: fsl-mc: Propagate driver_override for a child DPRC's children J. German Rivera
2015-06-09 21:59 ` [PATCH v4 4/7] staging: fsl-mc: Upgraded MC bus driver to match MC fw 7.0.0 J. German Rivera
2015-06-09 21:59 ` [PATCH v4 5/7] staging: fsl-mc: Allow the MC bus driver to run without GIC support J. German Rivera
2015-06-09 21:59 ` [PATCH v4 6/7] staging: fsl-mc: Add locking to serialize mc_send_command() calls J. German Rivera
2015-06-10 11:59   ` Dan Carpenter
2015-06-09 21:59 ` [PATCH v4 7/7] staging: fsl-mc: Use DPMCP IRQ and completion var to wait for MC J. German Rivera
2015-06-09 22:11 ` [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver Fabio Estevam
2015-06-09 23:07   ` Jose Rivera
2015-06-13  0:18 ` Greg KH
2015-06-13  8:46   ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Sudip Mukherjee
2015-06-13  8:58     ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver Sudip Mukherjee
2015-06-13 16:28     ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus dr Greg KH
2015-06-13 16:28       ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Greg KH
2015-06-13 16:57       ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus dr Joe Perches
2015-06-13 16:57         ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Joe Perches
2015-06-15  5:17         ` Sudip Mukherjee
2015-06-15  5:29           ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus dr Sudip Mukherjee
2015-06-15  6:36           ` Joe Perches
2015-06-15  6:36             ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Joe Perches
2015-06-19 10:29     ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus dr Dan Carpenter
2015-06-19 10:29       ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver) Dan Carpenter
2015-06-20 11:20       ` Sudip Mukherjee
2015-06-20 11:32         ` doubt about sm7xxfb (was: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus dr Sudip Mukherjee
2015-06-18 15:01   ` [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver Jose Rivera
2015-06-18 23:02     ` Greg KH [this message]

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=20150618230257.GC32238@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=German.Rivera@freescale.com \
    --cc=R89243@freescale.com \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=bhamciu1@freescale.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=itai.katz@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.erez@freescale.com \
    --cc=richard.schmitt@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.