From: "Kyrie Wu (吴晗)" <Kyrie.Wu@mediatek.com>
To: "Irui Wang (王瑞)" <Irui.Wang@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"Johnson Wang (王聖鑫)" <Johnson.Wang@mediatek.com>,
"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"tfiga@chromium.org" <tfiga@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Maoguang Meng (孟毛广)" <Maoguang.Meng@mediatek.com>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Xia Jiang (江霞)" <Xia.Jiang@mediatek.com>
Subject: Re: [PATCH] media: jpeg: refactor multi-hw judgement
Date: Fri, 16 Dec 2022 03:01:07 +0000 [thread overview]
Message-ID: <84660dde69fcf0293abacb922521c26329fc63f7.camel@mediatek.com> (raw)
In-Reply-To: <9a7434ba-2d42-cf15-334b-637b5f1b01a3@collabora.com>
On Thu, 2022-12-15 at 12:09 +0100, AngeloGioacchino Del Regno wrote:
> Il 15/12/22 11:50, Johnson Wang (王聖鑫) ha scritto:
> > On Thu, 2022-12-15 at 17:30 +0800, Irui Wang wrote:
> > > From: kyrie wu <kyrie.wu@mediatek.com>
> > >
> > > some chips have multi-hw, but others have only one,
> > > modify the condition of multi-hw judgement
> > >
> > > Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> > > Signed-off-by: irui wang <irui.wang@mediatek.com>
> > > ---
> > > drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 5 +++--
> > > drivers/media/platform/mtk-jpeg/mtk_jpeg_core.h | 12
> > > ++++++++++++
> > > 2 files changed, 15 insertions(+), 2 deletions(-)
> > >
> >
> > This may conflict with kernel mainline since mtk-jpeg folder
> > doesn't
> > exist.
> > Please fix it.
> >
> > BRs,
> > Johnson Wang
>
> Ouch. I just noticed that the folder is mismatching; this didn't
> deserve
> a R-b tag. I'll be more careful next time.
I'm terriable sorry for this mistake, and it would be fixed in the
coming version.
Thanks.
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-12-16 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:30 [PATCH] media: jpeg: refactor multi-hw judgement Irui Wang
2022-12-15 9:45 ` AngeloGioacchino Del Regno
2022-12-16 2:59 ` Kyrie Wu (吴晗)
2022-12-15 10:50 ` Johnson Wang (王聖鑫)
2022-12-15 11:09 ` AngeloGioacchino Del Regno
2022-12-16 3:01 ` Kyrie Wu (吴晗) [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=84660dde69fcf0293abacb922521c26329fc63f7.camel@mediatek.com \
--to=kyrie.wu@mediatek.com \
--cc=Irui.Wang@mediatek.com \
--cc=Johnson.Wang@mediatek.com \
--cc=Maoguang.Meng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Xia.Jiang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=tfiga@chromium.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