All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongling Zeng <zhongling0719@126.com>
To: Danilo Krummrich <dakr@kernel.org>,
	Hongling Zeng <zenghongling@kylinos.cn>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	simona@ffwll.ch, airlied@redhat.com, bskeggs@nvidia.com,
	dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] nouveau/gsp: Clean up IS_ERR vs IS_ERR_OR_NULL usage
Date: Mon, 22 Jun 2026 09:30:19 +0800	[thread overview]
Message-ID: <6A38902B.2080808@126.com> (raw)
In-Reply-To: <DJEQVST8KK4D.1DX65CF227WWC@kernel.org>

   Hi Danilo,
                 I've reviewed Sashiko's feedback and she's absolutely 
right about the documentation issues. I will send the v3 patch, However, 
I want to clarify that these are pre-existing issues in the  code, not 
problems introduced by my patch series， Unlike the previous kernel 
panic  issue  that we identified and fixed.

   Thanks,
   Hongling

在 2026年06月21日 21:00, Danilo Krummrich 写道:
> On Mon Jun 1, 2026 at 11:53 AM CEST, Hongling Zeng wrote:
>> >Hongling Zeng (5):
>> >   nouveau/gsp/rpc: Document RPC function return value contracts
>> >   nouveau/gsp/rpc: Cleanup incorrect IS_ERR_OR_NULL in rpc.c
>> >   nouveau/gsp/rm/alloc: Cleanup IS_ERR_OR_NULL usage
>> >   nouveau/gsp/rm/bar: Cleanup IS_ERR_OR_NULL usage
>> >   nouveau/gsp: Cleanup IS_ERR_OR_NULL in nvkm_gsp_rpc_rd()
> There are a few more comments from Sashiko, did you check them?
>
> Thanks,
> Danilo


WARNING: multiple messages have this Message-ID (diff)
From: Hongling Zeng <zhongling0719@126.com>
To: Danilo Krummrich <dakr@kernel.org>,
	 Hongling Zeng <zenghongling@kylinos.cn>
Cc: lyude@redhat.com, maarten.lankhorst@linux.intel.com,
	 mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
	 simona@ffwll.ch, airlied@redhat.com, ttabi@nvidia.com,
	 bskeggs@nvidia.com, dri-devel@lists.freedesktop.org,
	 nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] nouveau/gsp: Clean up IS_ERR vs IS_ERR_OR_NULL usage
Date: Mon, 22 Jun 2026 09:30:19 +0800	[thread overview]
Message-ID: <6A38902B.2080808@126.com> (raw)
In-Reply-To: <DJEQVST8KK4D.1DX65CF227WWC@kernel.org>

   Hi Danilo,
                 I've reviewed Sashiko's feedback and she's absolutely 
right about the documentation issues. I will send the v3 patch, However, 
I want to clarify that these are pre-existing issues in the  code, not 
problems introduced by my patch series， Unlike the previous kernel 
panic  issue  that we identified and fixed.

   Thanks,
   Hongling

在 2026年06月21日 21:00, Danilo Krummrich 写道:
> On Mon Jun 1, 2026 at 11:53 AM CEST, Hongling Zeng wrote:
>> >Hongling Zeng (5):
>> >   nouveau/gsp/rpc: Document RPC function return value contracts
>> >   nouveau/gsp/rpc: Cleanup incorrect IS_ERR_OR_NULL in rpc.c
>> >   nouveau/gsp/rm/alloc: Cleanup IS_ERR_OR_NULL usage
>> >   nouveau/gsp/rm/bar: Cleanup IS_ERR_OR_NULL usage
>> >   nouveau/gsp: Cleanup IS_ERR_OR_NULL in nvkm_gsp_rpc_rd()
> There are a few more comments from Sashiko, did you check them?
>
> Thanks,
> Danilo


  reply	other threads:[~2026-06-22  1:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  9:53 [PATCH v2 0/5] nouveau/gsp: Clean up IS_ERR vs IS_ERR_OR_NULL usage Hongling Zeng
2026-06-01  9:53 ` [PATCH v2 1/5] nouveau/gsp/rpc: Document RPC function return value contracts Hongling Zeng
2026-06-01  9:53   ` Hongling Zeng
2026-06-01  9:54 ` [PATCH v2 2/5] nouveau/gsp/rpc: Cleanup incorrect IS_ERR_OR_NULL in rpc.c Hongling Zeng
2026-06-01  9:54   ` Hongling Zeng
2026-06-01  9:54 ` [PATCH v2 3/5] nouveau/gsp/rm/alloc: Cleanup IS_ERR_OR_NULL usage Hongling Zeng
2026-06-01  9:54 ` [PATCH v2 4/5] nouveau/gsp/rm/bar: " Hongling Zeng
2026-06-01  9:54 ` [PATCH v2 5/5] nouveau/gsp: Cleanup IS_ERR_OR_NULL in nvkm_gsp_rpc_rd() Hongling Zeng
2026-06-01  9:54   ` Hongling Zeng
2026-06-21 13:00 ` [PATCH v2 0/5] nouveau/gsp: Clean up IS_ERR vs IS_ERR_OR_NULL usage Danilo Krummrich
2026-06-21 13:00   ` Danilo Krummrich
2026-06-22  1:30   ` Hongling Zeng [this message]
2026-06-22  1:30     ` Hongling Zeng

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=6A38902B.2080808@126.com \
    --to=zhongling0719@126.com \
    --cc=airlied@redhat.com \
    --cc=bskeggs@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=simona@ffwll.ch \
    --cc=zenghongling@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 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.