dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sunliming <sunliming@linux.dev>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: robin.clark@oss.qualcomm.com, lumag@kernel.org,
	airlied@gmail.com, simona@ffwll.ch, sean@poorly.run,
	marijn.suijten@somainline.org, linux-arm-msm@vger.kernel.org,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, sunliming <sunliming@kylinos.cn>,
	kernel test robot <lkp@intel.com>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH RESEND] drm/msm/dpu: Fix smatch warnings about variable dereferenced before check
Date: Mon, 2 Feb 2026 13:42:45 +0800	[thread overview]
Message-ID: <4f54e88e-7881-1072-1eea-99ae30a998a1@linux.dev> (raw)
In-Reply-To: <aXxqrD3ZzK_dTAmb@stanley.mountain>

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]


On 2026/1/30 16:24, Dan Carpenter wrote:
> On Fri, Jan 30, 2026 at 01:30:35PM +0800, sunliming wrote:
>> On 2026/1/29 15:07, Dan Carpenter wrote:
>>> On Thu, Jan 29, 2026 at 10:49:19AM +0800,sunliming@linux.dev   wrote:
>>>> From: sunliming<sunliming@kylinos.cn>
>>>>
>>>> Fix below smatch warnings:
>>>> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp_v13.c:161 dpu_hw_sspp_setup_pe_config_v13()
>>>> warn: variable dereferenced before check 'ctx' (see line 159)
>>>>
>>>> Reported-by: kernel test robot<lkp@intel.com>
>>>> Reported-by: Dan Carpenter<error27@gmail.com>
>>>> Closes:https://lore.kernel.org/r/202601252214.oEaY3UZM-lkp@intel.com/
>>>> Signed-off-by: sunliming<sunliming@kylinos.cn>
>>>> ---
>> Previously, a maintainer suggested that the name should match the email
>> address,
>>
> Yes.  But normally people change their email address instead of their
> name.
>
>> but community patches have consistently used the name "sunliming" since
>> then.
>>
> Consistency is less important than being correct...  It's just a weird
> thing to say.  Are there other non-community patches with a different
> name?  It's fine if that's your legal name and we have made exceptions
> for people who aren't able to share their real name because of stalking
> or whatever...

I have no non-community patches using any other name, and the accounts in

other systems at my employer also use this name. Thanks.

> regards,
> dan carpenter
>

[-- Attachment #2: Type: text/html, Size: 4557 bytes --]

  reply	other threads:[~2026-02-02  5:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  2:49 [PATCH RESEND] drm/msm/dpu: Fix smatch warnings about variable dereferenced before check sunliming
2026-01-29  7:07 ` Dan Carpenter
2026-01-30  5:30   ` sunliming
2026-01-30  8:24     ` Dan Carpenter
2026-02-02  5:42       ` sunliming [this message]
2026-01-31  8:29     ` Dmitry Baryshkov
2026-01-31  8:30 ` Dmitry Baryshkov
2026-02-01 17:04 ` Rob Clark

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=4f54e88e-7881-1072-1eea-99ae30a998a1@linux.dev \
    --to=sunliming@linux.dev \
    --cc=airlied@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=error27@gmail.com \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=sunliming@kylinos.cn \
    /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