From: Dan Carpenter <dan.carpenter@linaro.org>
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [bug report] staging: sm750fb: Fix polarity assignment for vertical and horizontal mode
Date: Thu, 31 Jul 2025 19:11:15 +0300 [thread overview]
Message-ID: <dbd2df69-27cc-4fd8-8e5b-78b6872d5d16@suswa.mountain> (raw)
In-Reply-To: <20250723192528.77109-1-alok.a.tiwari@oracle.com>
On Wed, Jul 23, 2025 at 12:24:31PM -0700, Alok Tiwari wrote:
> In drivers/staging/sm750fb/sm750_hw.c,
> the vertical and horizontal sync polarity assignments were incorrectly
> ordered.
> The assignment for modparm.vertical_sync_polarity was mistakenly using
> the FB_SYNC_HOR_HIGH_ACT bit instead of FB_SYNC_VERT_HIGH_ACT,
> and the horizontal polarity line was commented out or missing.
>
> This patch corrects the logic by properly assigning:
>
> vertical_sync_polarity -> from FB_SYNC_VERT_HIGH_ACT
> horizontal_sync_polarity -> from FB_SYNC_HOR_HIGH_ACT
>
> Please let me know your feedback.
> Thanks,
> Alok
> ---
> Fixes: 81dee67e215b ("staging: sm750fb: add sm750 to staging")
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
> ---
Did you find this copy and paste bug by testing or reviewing the code?
How does this bug look like to a user? Please put that in your commit
message.
This looks reasonable to me, but the patch is badly formatted.
1) It should say [PATCH] in the subject.
2) The body of the email should be the commit message.
3) the --- should only come after the Signed-off-by line.
Try applying your patch with `git am` and review the log to see what I
mean.
regards,
dan carpenter
next prev parent reply other threads:[~2025-07-31 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 19:24 [bug report] staging: sm750fb: Fix polarity assignment for vertical and horizontal mode Alok Tiwari
2025-07-31 16:11 ` Dan Carpenter [this message]
2025-07-31 16:33 ` [External] : " ALOK TIWARI
2025-07-31 18:13 ` Dan Carpenter
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=dbd2df69-27cc-4fd8-8e5b-78b6872d5d16@suswa.mountain \
--to=dan.carpenter@linaro.org \
--cc=alok.a.tiwari@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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