From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: David Miller <davem@davemloft.net>
Cc: Leo Li <leoyang.li@nxp.com>, Roy Pledge <roy.pledge@nxp.com>,
Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
Horia Geanta <horia.geanta@nxp.com>,
"brouer@redhat.com" <brouer@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing
Date: Mon, 25 Feb 2019 07:00:28 +0000 [thread overview]
Message-ID: <VI1PR0402MB280056BBF62A86E1703C549BE07A0@VI1PR0402MB2800.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190224.220653.256212672271785631.davem@davemloft.net>
> Subject: Re: [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing
>
> From: Ioana Ciornei <ioana.ciornei@nxp.com>
> Date: Sat, 23 Feb 2019 08:48:42 +0000
>
> > The first two patches enable cache stashing and configure the core
> > cluster destination per software portal while the third patch is the
> > one configuring the amount of stashing on a queue.
>
> Should I merge this series in via my networking tree?
Even though it would be really good to have this on the networking tree as soon as possible, I am afraid that patch 2/3 is not going to apply cleanly because it touches the same areas of code that some other patches on Leo's tree are.
Thanks,
Ioana C
next prev parent reply other threads:[~2019-02-25 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 8:48 [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing Ioana Ciornei
2019-02-23 8:48 ` [PATCH 1/3] soc: fsl: dpio: enable frame data cache stashing per software portal Ioana Ciornei
2019-02-23 8:48 ` [PATCH 2/3] soc: fsl: dpio: configure cache stashing destination Ioana Ciornei
2019-02-23 8:48 ` [PATCH 3/3] dpaa2-eth: configure the cache stashing amount on a queue Ioana Ciornei
2019-02-25 6:06 ` [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing David Miller
2019-02-25 7:00 ` Ioana Ciornei [this message]
2019-02-26 19:03 ` Li Yang
2019-02-26 20:31 ` David Miller
2019-02-26 23:42 ` Li Yang
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=VI1PR0402MB280056BBF62A86E1703C549BE07A0@VI1PR0402MB2800.eurprd04.prod.outlook.com \
--to=ioana.ciornei@nxp.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=horia.geanta@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).