On 1/19/2017 6:30 AM, Andrew Rybchenko wrote:
> On 01/19/2017 08:53 AM, Jerin Jacob wrote:
>> On Wed, Jan 18, 2017 at 07:31:39PM +, Ferruh Yigit wrote:
>>> Hi Andrew, Jerin,
>>>
>>> Existing "I/O device memory read/write" doesn't cover sfc driver because
>>> driver was in next-net tree.
>>>
>>>
On 01/19/2017 08:53 AM, Jerin Jacob wrote:
On Wed, Jan 18, 2017 at 07:31:39PM +, Ferruh Yigit wrote:
Hi Andrew, Jerin,
Existing "I/O device memory read/write" doesn't cover sfc driver because
driver was in next-net tree.
And both sfc and "I/O device memory read/write" patches will be
integ
On Wed, Jan 18, 2017 at 07:31:39PM +, Ferruh Yigit wrote:
> Hi Andrew, Jerin,
>
> Existing "I/O device memory read/write" doesn't cover sfc driver because
> driver was in next-net tree.
>
> And both sfc and "I/O device memory read/write" patches will be
> integrated into main tree for rc1 rel
Hi Andrew, Jerin,
Existing "I/O device memory read/write" doesn't cover sfc driver because
driver was in next-net tree.
And both sfc and "I/O device memory read/write" patches will be
integrated into main tree for rc1 release.
If "I/O device memory read/write" implementation can be done for sfc
4 matches
Mail list logo