From: Greg KH <gregkh@linuxfoundation.org>
To: Stuart Yoder <stuart.yoder@nxp.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"agraf@suse.de" <agraf@suse.de>, "arnd@arndb.de" <arnd@arndb.de>,
German Rivera <german.rivera@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>
Subject: Re: [PATCH 00/14] staging: fsl-mc: cleanup and uprev to MC v10.x
Date: Tue, 25 Oct 2016 20:09:41 +0200 [thread overview]
Message-ID: <20161025180941.GA17363@kroah.com> (raw)
In-Reply-To: <VI1PR0401MB263891283E9A573C1A7F407A8DA80@VI1PR0401MB2638.eurprd04.prod.outlook.com>
On Tue, Oct 25, 2016 at 03:43:56PM +0000, Stuart Yoder wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Tuesday, October 25, 2016 2:50 AM
> > To: Stuart Yoder <stuart.yoder@nxp.com>
> > Cc: German Rivera <german.rivera@nxp.com>; devel@driverdev.osuosl.org; linux-kernel@vger.kernel.org;
> > agraf@suse.de; arnd@arndb.de; Leo Li <leoyang.li@nxp.com>
> > Subject: Re: [PATCH 00/14] staging: fsl-mc: cleanup and uprev to MC v10.x
> >
> > On Mon, Oct 17, 2016 at 01:42:09PM -0500, Stuart Yoder wrote:
> > > This patch does miscellaneous minor cleanup and uprevs the supported
> > > MC firmware version to 10.x.
> > >
> > > I believe with this series the TODO items on our list are complete,
> > > with the exception of "Add at least one device driver for a DPAA2
> > > object", which I expect to send a patch for very soon. I plan to
> > > do that in conjunction with a request to move the fsl-mc bus
> > > driver out of staging.
> >
> > I applied some of these patches, can you rebase and fix up and resend
> > the remaining ones?
>
> Yes, will resend.
>
> Regarding the patch:
> [PATCH 14/14] staging: fsl-mc: uprev binary interface to match MC v10.x
>
> ...your comment was that it did a lot of different things at once. In
> this case, there is no way for me to break that up. The things listed
> in that patch were the changes to the binary interface of the hardware,
> and to match it we have to change everything at once.
Ah, ok, make that a bit more specific in the patch changelog text so I
don't ask the same thing when you resend it and I re-review it :)
thanks,
greg k-h
prev parent reply other threads:[~2016-10-25 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:42 [PATCH 00/14] staging: fsl-mc: cleanup and uprev to MC v10.x Stuart Yoder
2016-10-25 7:50 ` Greg KH
2016-10-25 15:43 ` Stuart Yoder
2016-10-25 18:09 ` 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=20161025180941.GA17363@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=german.rivera@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@nxp.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.