linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: LiangCheng Wang <zaq14760@gmail.com>
To: andy@kernel.org
Cc: zaq14760@gmail.com, hansg@kernel.org, mchehab@kernel.org,
	sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH v4] staging: media: atomisp: fix coding style in ia_css_output.host.c
Date: Tue, 24 Jun 2025 23:19:58 +0800	[thread overview]
Message-ID: <20250624152000.489-1-zaq14760@gmail.com> (raw)
In-Reply-To: <CAHp75Ve_G=ziR7sJmKw4t3BRASogGQ1kWUsNNNWESFmmS4rVhw@mail.gmail.com>

Subject: Re: [PATCH v4] staging: media: atomisp: fix coding style in ia_css_output.host.c
In-Reply-To: <CAHp75Ve_G=ziR7sJmKw4t3BRASogGQ1kWUsNNNWESFmmS4rVhw@mail.gmail.com>

Dear Andy,

Thank you for your suggestion.

You're right — the driver is quite large and contains many similar issues.  
To keep the patches manageable and easier to review, I plan to split the cleanup into multiple smaller patches.  
I'll start by submitting a series of patches, each focusing on a specific file or type of issue.

Since I’m contributing in my free time outside of work, I may need to spread the cleanup over several days.  
I’ll do my best to keep the patches consistent and focused.

Thanks again for your guidance.

Best regards,  
LiangCheng Wang

  parent reply	other threads:[~2025-06-24 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 14:10 [PATCH v4] staging: media: atomisp: fix coding style in ia_css_output.host.c LiangCheng Wang
2025-06-24 14:14 ` Andy Shevchenko
2025-06-24 14:32   ` LiangCheng Wang
2025-06-24 15:19   ` LiangCheng Wang [this message]
2025-06-24 18:12     ` Andy Shevchenko

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=20250624152000.489-1-zaq14760@gmail.com \
    --to=zaq14760@gmail.com \
    --cc=andy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.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 NNTP newsgroup(s).