From: Markus Elfring <Markus.Elfring@web.de>
To: vulab@iscas.ac.cn, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
David Airlie <airlied@gmail.com>, Inki Dae <inki.dae@samsung.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH] drm/exynos/vidi: Remove redundant error handling in vidi_get_modes()
Date: Fri, 7 Mar 2025 15:48:37 +0100 [thread overview]
Message-ID: <c29a5d6e-335b-463e-a318-e8d78d176a9f@web.de> (raw)
In-Reply-To: <20250306042720.2296-1-vulab@iscas.ac.cn>
…
> drm_edid_alloc() fails, the function will immediately return 0,
…
failed?
…
> the event of failure in these two functions, it is still necessary
> to call the subsequent drm_edid_connector_update() function with
…
You may occasionally put more than 66 characters into text lines
of such a change description.
> … To maintain the integrity of
> the operation, redundant error handling needs to be removed.
How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14-rc5#n145
Regards,
Markus
next prev parent reply other threads:[~2025-03-07 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250306042753epcas1p3983510872a862109f7f72aff5d074ea3@epcas1p3.samsung.com>
2025-03-06 4:27 ` [PATCH] drm/exynos/vidi: Remove redundant error handling in vidi_get_modes() Wentao Liang
2025-03-07 14:48 ` Markus Elfring [this message]
2025-03-19 3:30 ` 대인기/Tizen Platform Lab(SR)/삼성전자
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=c29a5d6e-335b-463e-a318-e8d78d176a9f@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jani.nikula@linux.intel.com \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=sw0312.kim@samsung.com \
--cc=vulab@iscas.ac.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