Linux kernel staging patches
 help / color / mirror / Atom feed
From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jack Zhu <jack.zhu@starfivetech.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>
Subject: 回复: 回复: [v1] staging: media: starfive: Clean pad selection in isp_try_format()
Date: Fri, 19 Apr 2024 01:17:38 +0000	[thread overview]
Message-ID: <SHXPR01MB0671B2D3F26A593730FD2A9DF20DA@SHXPR01MB0671.CHNPR01.prod.partner.outlook.cn> (raw)
In-Reply-To: <ea244234-38f0-4381-9c9a-b6c6076e7dcb@moroto.mountain>

Hi, dan

> On Thu, Apr 18, 2024 at 01:27:04AM +0000, Changhuang Liang wrote:
> > Hi, Hans
> >
> > > The code to select isp_dev->formats[] is overly complicated.  We can
> > > just use the "pad" as the index.  This will making adding new pads
> > > easier in future patches.  No functional change.
> > >
> > > Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> > > ---
> >
> > Could you please help to review this patch, thanks for your time.
> 
> Linux-media uses patchwork, so probably it was missed because it didn't have
> a [PATCH] in the subject.  Just resend.
> 

But I can find it in the patchwork:
https://patchwork.linuxtv.org/project/linux-media/list/?param=3&page=4

regards,
Changhuang

      reply	other threads:[~2024-04-19  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  2:45 [v1] staging: media: starfive: Clean pad selection in isp_try_format() Changhuang Liang
2024-03-13  6:01 ` Dan Carpenter
2024-04-18  1:27 ` 回复: " Changhuang Liang
2024-04-18 17:19   ` Dan Carpenter
2024-04-19  1:17     ` Changhuang Liang [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=SHXPR01MB0671B2D3F26A593730FD2A9DF20DA@SHXPR01MB0671.CHNPR01.prod.partner.outlook.cn \
    --to=changhuang.liang@starfivetech.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jack.zhu@starfivetech.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).