mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: huanglei  <huanglei814@163.com>
To: linux-media@vger.kernel.org
Cc: "Linux Media CI" <media-ci@linuxtv.org>,
	hverkuil+cisco@kernel.org, johan@kernel.org, mchehab@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [v3,0/2] media: s2255: Fix firmware parsing OOB and cleanup coding style
Date: Thu, 16 Jul 2026 20:32:47 +0800 (CST)	[thread overview]
Message-ID: <feb382c.8c2b.19f6aea4d68.Coremail.huanglei814@163.com> (raw)
In-Reply-To: <6a587498.8e904814.3310e.980c@mx.google.com>

Hi,

Thanks a lot for your review feedback. This version of the patch series is submitted ‌fully in strict accordance with maintainer suggestions‌:

 The critical functional fix media: s2255: check firmware size before reading trailing marker is placed as the first patch independently. It resolves the out-of-bounds read vulnerability completely with no unrelated style changes, which is very convenient for direct stable backporting.
 The subsequent media: s2255: Rename CamelCase goto labels to snake_case cleanup patch is placed on top of the fix, as a separate pure non-functional commit to unify all the error path labels to comply with kernel coding style.

This ordering and split of commits fully follow maintainer advice to make the series easy to merge, review and backport. The final applied state has no remaining non-standard CamelCase labels and meets Linux kernel coding style requirements.

For the earlier CI CamelCase warning, it only exists temporarily on the first independent fix patch, and the full series after the two patches are applied will eliminate all such non-standard naming.


On 15/07/2026 12:00, Johan Hovold wrote:
> This looks ok, but the fix should go before the cleanup (e.g. to
> facilitate backporting).


At 2026-07-16 13:05:12, "Patchwork Integration" <patchwork@media-ci.org> wrote:
>Dear Lei Huang:
>
>Thanks for your patches! Unfortunately the Media CI robot detected some
>issues:
>
># Test checkpatch:./0001-media-s2255-check-firmware-size-before-reading-trail.patch checkpatch
>CHECK: Avoid CamelCase: <errorFWMARKER>
>#30: FILE: drivers/media/usb/s2255/s2255drv.c:2283:
>+goto errorFWMARKER;
>
>total: 0 errors, 0 warnings, 1 checks, 11 lines checked
>
>
>
>Please fix your series, and upload a new version. If you have a patchwork
>account, do not forget to mark the current series as Superseded.
>
>For more details, check the full report at:
>https://linux-media.pages.freedesktop.org/-/users/patchwork/-/jobs/105100498/artifacts/report.htm .
>
>
>
>Best regards, and Happy Hacking!
>Media CI robot on behalf of the linux-media community.
>
>---
>Check the latest rules for contributing your patches at:
>https://docs.kernel.org/driver-api/media/maintainer-entry-profile.html
>
>If you believe that the CI is wrong, kindly open an issue at
>https://gitlab.freedesktop.org/linux-media/media-ci/-/issues or reply-all
>to this message.

      parent reply	other threads:[~2026-07-16 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16  2:23 [PATCH v3 0/2] " Lei Huang
2026-07-16  2:23 ` [PATCH v3 1/2] media: s2255: check firmware size before reading trailing marker Lei Huang
     [not found] ` <6a587498.8e904814.3310e.980c@mx.google.com>
2026-07-16 12:32   ` huanglei [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=feb382c.8c2b.19f6aea4d68.Coremail.huanglei814@163.com \
    --to=huanglei814@163.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=media-ci@linuxtv.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

all inboxes | Powered by JetHome®