From: Hui Fang <hui.fang@nxp.com>
To: "tfiga@chromium.org" <tfiga@chromium.org>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"mchehab@kernel.org" <mchehab@kernel.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Anle Pan <anle.pan@nxp.com>, Xuegang Liu <xuegang.liu@nxp.com>,
"arakesh@google.com" <arakesh@google.com>,
"jchowdhary@google.com" <jchowdhary@google.com>,
"rdhanjal@google.com" <rdhanjal@google.com>
Subject: RE: [PATCH] MA-21654 Use dma_alloc_pages in vb2_dma_sg_alloc_compacted
Date: Mon, 18 Sep 2023 02:20:23 +0000 [thread overview]
Message-ID: <DB9PR04MB928463A0FC0EEAB681763B7F87FBA@DB9PR04MB9284.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DB9PR04MB928456C515C3D53744A04B1087F7A@DB9PR04MB9284.eurprd04.prod.outlook.com>
On Thu, Sep 14, 2023 at 15:52 PM Fang Hui <hui.fang@nxp.com> wrote:
> Two things.
> 1. For dma_data_direction para (DMA_BIDIRECTIONAL is used) of
> dma_alloc_pages(),
> maybe better pass from callers? In DeviceAsWebcam case, it's
> DMA_TO_DEVICE.
>
> 2. "MA-21654" (NXP ticket number) should be removed in the comment, need
> I re-push or it will be done on your side, thanks!
Keep google friends in the loop.
BRs,
Fang Hui
next prev parent reply other threads:[~2023-09-18 2:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 14:58 [PATCH] MA-21654 Use dma_alloc_pages in vb2_dma_sg_alloc_compacted Fang Hui
2023-09-14 7:52 ` Hui Fang
2023-09-18 2:20 ` Hui Fang [this message]
2023-09-18 7:07 ` Hui Fang
2023-09-18 23:43 ` kernel test robot
2023-09-19 6:43 ` [EXT] " Hui Fang
2023-09-19 19:04 ` Nicolas Dufresne
2023-09-20 7:41 ` Tomasz Figa
2023-09-20 10:02 ` [EXT] " Hui Fang
2023-09-20 16:54 ` Robin Murphy
2023-09-21 8:35 ` Tomasz Figa
2023-09-26 6:51 ` Christoph Hellwig
2023-09-26 8:21 ` Robin Murphy
2023-09-26 9:46 ` Christoph Hellwig
2023-09-26 14:38 ` Robin Murphy
2023-12-28 7:46 ` Tomasz Figa
2024-05-13 9:49 ` [EXT] " Hui Fang
2024-05-21 0:35 ` Tomasz Figa
2023-09-26 6:50 ` Christoph Hellwig
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=DB9PR04MB928463A0FC0EEAB681763B7F87FBA@DB9PR04MB9284.eurprd04.prod.outlook.com \
--to=hui.fang@nxp.com \
--cc=anle.pan@nxp.com \
--cc=arakesh@google.com \
--cc=jchowdhary@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=rdhanjal@google.com \
--cc=tfiga@chromium.org \
--cc=xuegang.liu@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 read-only IMAP folder(s) and NNTP newsgroup(s).