From: Markus Elfring <Markus.Elfring@web.de>
To: Alexandr Sapozhnikov <alsp705@gmail.com>,
dri-devel@lists.freedesktop.org, lvc-project@linuxtesting.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2] vgem: fix error return in vgem_init()
Date: Fri, 3 Oct 2025 16:42:11 +0200 [thread overview]
Message-ID: <1afdfccc-04f1-4f82-a1bf-bf93df42af29@web.de> (raw)
In-Reply-To: <20251002091844.11-1-alsp705@gmail.com>
> The dma_coerce_mask_and_coherent function may
> fail to apply a mask due to incorrectly passed parameters.
…
* You may occasionally put more than 61 characters into text lines
of such a change description.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17#n658
* Would you like to choose another imperative wording?
* How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
…
> ---
> drivers/gpu/drm/vgem/vgem_drv.c | 4 +++-
…
Some contributors would appreciate patch version descriptions.
https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
…
> +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> @@ -140,8 +140,10 @@ static int __init vgem_init(void)
> goto out_unregister;
> }
>
> - dma_coerce_mask_and_coherent(&pdev->dev,
> + ret = dma_coerce_mask_and_coherent(&pdev->dev,
> DMA_BIT_MASK(64));
> + if (ret)
> + goto out_unregister;
…
I suggest to keep the passed parameters in the same line for this function call.
Regards,
Markus
prev parent reply other threads:[~2025-10-03 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:18 Alexandr Sapozhnkiov
2025-10-03 14:42 ` Markus Elfring [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=1afdfccc-04f1-4f82-a1bf-bf93df42af29@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=alsp705@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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®