From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
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>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v11 1/6] page_pool: fragment API support for 32-bit arch with 64-bit DMA
Date: Tue, 17 Oct 2023 16:02:40 +0300 [thread overview]
Message-ID: <CAC_iWjLYZWUt9RFkAMR8=2amscbOUqXbVP8n8oiXHGsXw-ZKCA@mail.gmail.com> (raw)
In-Reply-To: <e738b0b9-6c60-b971-7fd9-0ec1b14dda3c@huawei.com>
Hi Yunsheng
On Tue, 17 Oct 2023 at 15:53, Yunsheng Lin <linyunsheng@huawei.com> wrote:
>
> On 2023/10/17 20:17, Ilias Apalodimas wrote:
> >>
> >
> > That looks fine wrt what we discussed with Jakub,
> >
> > Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
>
> Thanks. What about other patches in this series? Could you take
> some time to review them too?
Yes I will, I was on nonstop trips, and was a bit cumbersome to
review/test. Also, there Plumbers is in a month, and I have an idea I
need to discuss with Jakub about adding page pool patches to a CI.
That should make the whole process a bit faster
Thanks
/Ilias
>
> >
> > .
> >
prev parent reply other threads:[~2023-10-17 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231013064827.61135-1-linyunsheng@huawei.com>
2023-10-13 6:48 ` Yunsheng Lin
2023-10-17 1:31 ` Jakub Kicinski
2023-10-17 12:05 ` Ilias Apalodimas
2023-10-17 12:17 ` Ilias Apalodimas
2023-10-17 12:53 ` Yunsheng Lin
2023-10-17 13:02 ` Ilias Apalodimas [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='CAC_iWjLYZWUt9RFkAMR8=2amscbOUqXbVP8n8oiXHGsXw-ZKCA@mail.gmail.com' \
--to=ilias.apalodimas@linaro.org \
--cc=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=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