linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Alexander Duyck <alexander.duyck@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>, <davem@davemloft.net>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	"Liang Chen" <liangchen.linux@gmail.com>,
	Guillaume Tucker <guillaume.tucker@collabora.com>,
	Matthew Wilcox <willy@infradead.org>,
	Linux-MM <linux-mm@kvack.org>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v10 1/6] page_pool: fragment API support for 32-bit arch with 64-bit DMA
Date: Tue, 10 Oct 2023 19:49:13 +0200	[thread overview]
Message-ID: <476acf0a-afdf-455d-a127-320109604ce7@intel.com> (raw)
In-Reply-To: <943e7a57-1285-4123-578c-1bb8d1a926c4@huawei.com>

From: Yunsheng Lin <linyunsheng@huawei.com>
Date: Sun, 8 Oct 2023 17:36:59 +0800

> On 2023/10/4 17:31, Alexander Lobakin wrote:
>> From: Jakub Kicinski <kuba@kernel.org>
>> Date: Tue, 3 Oct 2023 15:12:16 -0700
>>
>>> On Tue, 03 Oct 2023 09:45:56 +0200 Paolo Abeni wrote:
>>>> I think it would be nice also an explicit ack from Jesper and/or Ilias.
>>>
>>> Also a review tag from one or both of the Alexanders would be great!
>>
>> I got back to libie/iavf this week, hoping I'll rebase without major
>> issues and will be able to give a Tested-by as well, will see :>
>>
> 
> It is great to have some Tested-by tag to confirm that this patchset
> works for other driver. Please let me know if there is any problem when
> rebasing and testing, thanks.

IAVF with PP on the latest net-next from [0]:

Tested-by: Alexander Lobakin <aleksander.lobakin@intel.com>

Still some stuff on my side to fix/improve before submitting a new
revision of libie / PP for IAVF, but at least the current code works
just as expected.

> 
> 
>> Thanks,
>> Olek
>>
>> .
>>

[0] https://github.com/alobakin/linux/commits/iavf-pp-frag

Thanks,
Olek


      reply	other threads:[~2023-10-10 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230922091138.18014-1-linyunsheng@huawei.com>
2023-09-22  9:11 ` [PATCH net-next v10 1/6] page_pool: fragment API support for 32-bit arch with 64-bit DMA Yunsheng Lin
2023-10-03  7:45   ` Paolo Abeni
2023-10-03  9:40     ` Ilias Apalodimas
2023-10-03 22:12     ` Jakub Kicinski
2023-10-04  9:31       ` Alexander Lobakin
2023-10-08  9:36         ` Yunsheng Lin
2023-10-10 17:49           ` Alexander Lobakin [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=476acf0a-afdf-455d-a127-320109604ce7@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kuba@kernel.org \
    --cc=liangchen.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linyunsheng@huawei.com \
    --cc=lorenzo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willy@infradead.org \
    /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).