linux-kernel - Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus driver

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]

Date:	Thu, 18 Jun 2015 16:02:57 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Jose Rivera <German.Rivera@...escale.com>
Cc:	"arnd@...db.de" <arnd@...db.de>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Stuart Yoder <stuart.yoder@...escale.com>,
	Sharma Bhupesh <bhupesh.sharma@...escale.com>,
	"agraf@...e.de" <agraf@...e.de>,
	Hamciuc Bogdan <bhamciu1@...escale.com>,
	Erez Nir <nir.erez@...escale.com>,
	Katz Itai <itai.katz@...escale.com>,
	Scott Wood <scottwood@...escale.com>,
	Marginean Alexandru <R89243@...escale.com>,
	"dan.carpenter@...cle.com" <dan.carpenter@...cle.com>,
	Richard Schmitt <richard.schmitt@...escale.com>
Subject: Re: [PATCH v4 0/7] staging: fsl-mc: New functionality to the MC bus
 driver

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
--
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/