From: Matthias Brugger <matthias.bgg@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] media: mediatek: vcodec: Remove trailing space after \n newline
Date: Mon, 2 Sep 2024 17:06:37 +0200 [thread overview]
Message-ID: <cc3e30c6-3e97-4db8-a978-9c2048bfad0e@gmail.com> (raw)
In-Reply-To: <20240902140758.308202-1-colin.i.king@gmail.com>
On 02/09/2024 16:07, Colin Ian King wrote:
> There is a extraneous space after a newline in a mtk_venc_debug message.
> Remove it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> .../media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c b/drivers/media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c
> index f8145998fcaf..59e56b81d5e0 100644
> --- a/drivers/media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c
> +++ b/drivers/media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c
> @@ -515,7 +515,7 @@ static int h264_encode_frame(struct venc_h264_inst *inst,
> struct venc_frame_info frame_info;
> struct mtk_vcodec_enc_ctx *ctx = inst->ctx;
>
> - mtk_venc_debug(ctx, "frm_cnt = %d\n ", inst->frm_cnt);
> + mtk_venc_debug(ctx, "frm_cnt = %d\n", inst->frm_cnt);
>
> if (MTK_ENC_IOVA_IS_34BIT(ctx)) {
> gop_size = inst->vsi_34->config.gop_size;
prev parent reply other threads:[~2024-09-02 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 14:07 Colin Ian King
2024-09-02 15:06 ` Matthias Brugger [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=cc3e30c6-3e97-4db8-a978-9c2048bfad0e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--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=mchehab@kernel.org \
--cc=tiffany.lin@mediatek.com \
--cc=yunfei.dong@mediatek.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
all inboxes | Powered by JetHome®