All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: Add a missing semi-colon
Date: Mon, 01 Mar 2021 19:59:43 +0000	[thread overview]
Message-ID: <161462878383.6187.85563575723121248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210207041858.3317171-1-swboyd@chromium.org>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Sat,  6 Feb 2021 20:18:58 -0800 you wrote:
> A missing semicolon here causes my external display to stop working.
> Indeed, missing the semicolon on the return statement leads to
> dp_panel_update_tu_timings() not existing because the compiler thinks
> it's part of the return statement of a void function, so it must not be
> important.
> 
>   $ ./scripts/bloat-o-meter before.o after.o
>   add/remove: 1/1 grow/shrink: 0/1 up/down: 7400/-7540 (-140)
>   Function                                     old     new   delta
>   dp_panel_update_tu_timings                     -    7400   +7400
>   _dp_ctrl_calc_tu.constprop                 18024   17900    -124
>   dp_panel_update_tu_timings.constprop        7416       -   -7416
>   Total: Before=54440, After=54300, chg -0.26%
> 
> [...]

Here is the summary with links:
  - drm/msm/dp: Add a missing semi-colon
    https://git.kernel.org/qcom/c/182b4a2d2513

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07  4:18 [PATCH] drm/msm/dp: Add a missing semi-colon Stephen Boyd
2021-02-07  4:18 ` Stephen Boyd
2021-02-07  5:06 ` Joe Perches
2021-02-07  5:06   ` Joe Perches
2021-02-08 18:57   ` Stephen Boyd
2021-02-08 18:57     ` Stephen Boyd
2021-02-12  9:43     ` Joe Perches
2021-02-12  9:43       ` Joe Perches
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878383.6187.85563575723121248.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.