All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Suarez <cssk@net-c.es>
To: dri-devel@lists.freedesktop.org, 0day robot <lkp@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>
Subject: Re: [PATCH v2] drm: fix error found in some cases after the patch d1af5cd86997
Date: Tue, 21 Dec 2021 23:55:26 +0100	[thread overview]
Message-ID: <YcJbXva93zJJBGbE@gineta.localdomain> (raw)
In-Reply-To: <YcC5Qxnj8PvqnS6f@phenom.ffwll.local>

On Mon, Dec 20, 2021 at 06:11:31PM +0100, Daniel Vetter wrote:
> On Mon, Dec 20, 2021 at 10:18:38AM +0100, Daniel Vetter wrote:
> > On Thu, Dec 02, 2021 at 10:51:12AM +0100, Claudio Suarez wrote:
> > > The patch d1af5cd86997 ("drm: get rid of DRM_DEBUG_* log
> > > calls in drm core, files drm_a*.c") fails when the drm_device
> > > cannot be found in the parameter plane_state->crtc.
> > > Fix it using plane_state->plane.
> > > 
> > > Reported-by: kernel test robot <oliver.sang@intel.com>
> > > Fixes: d1af5cd86997 ("drm: get rid of DRM_DEBUG_* log calls in drm core, files drm_a*.c")
> 
> My scrip complained about the fixes line, so I fixed it. I guess you've
> used the sha1 from your tree, not from upstream?

Yes, my bad, sorry. Thanks for the advice.

> Please always use
> upstream sha1 when referencing commits.
> 
> Anyway patches are now pushed.

Thank you!

Best regards.
Claudio Suarez.




WARNING: multiple messages have this Message-ID (diff)
From: Claudio Suarez <cssk@net-c.es>
To: lkp@lists.01.org
Subject: Re: [PATCH v2] drm: fix error found in some cases after the patch d1af5cd86997
Date: Tue, 21 Dec 2021 23:55:26 +0100	[thread overview]
Message-ID: <YcJbXva93zJJBGbE@gineta.localdomain> (raw)
In-Reply-To: <YcC5Qxnj8PvqnS6f@phenom.ffwll.local>

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

On Mon, Dec 20, 2021 at 06:11:31PM +0100, Daniel Vetter wrote:
> On Mon, Dec 20, 2021 at 10:18:38AM +0100, Daniel Vetter wrote:
> > On Thu, Dec 02, 2021 at 10:51:12AM +0100, Claudio Suarez wrote:
> > > The patch d1af5cd86997 ("drm: get rid of DRM_DEBUG_* log
> > > calls in drm core, files drm_a*.c") fails when the drm_device
> > > cannot be found in the parameter plane_state->crtc.
> > > Fix it using plane_state->plane.
> > > 
> > > Reported-by: kernel test robot <oliver.sang@intel.com>
> > > Fixes: d1af5cd86997 ("drm: get rid of DRM_DEBUG_* log calls in drm core, files drm_a*.c")
> 
> My scrip complained about the fixes line, so I fixed it. I guess you've
> used the sha1 from your tree, not from upstream?

Yes, my bad, sorry. Thanks for the advice.

> Please always use
> upstream sha1 when referencing commits.
> 
> Anyway patches are now pushed.

Thank you!

Best regards.
Claudio Suarez.



  reply	other threads:[~2021-12-21 22:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 10:49 [PATCH] drm: get rid of DRM_DEBUG_* log calls in drm core, files drm_a*.c Claudio Suarez
2021-11-26 15:45 ` Daniel Vetter
2021-11-26 21:57   ` Claudio Suarez
2021-11-28 14:20 ` [drm] d1af5cd869: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2021-11-28 14:20   ` kernel test robot
2021-11-28 14:20   ` kernel test robot
2021-11-29 19:27   ` [PATCH] drm: fix error found in some cases after the patch d1af5cd86997 Claudio Suarez
2021-11-29 19:27     ` Claudio Suarez
2021-11-29 19:27     ` Claudio Suarez
2021-11-30  8:38     ` Daniel Vetter
2021-11-30  8:38       ` Daniel Vetter
2021-11-30  8:38       ` Daniel Vetter
2021-12-02  9:44       ` Claudio Suarez
2021-12-02  9:44         ` Claudio Suarez
2021-12-02  9:49         ` [PATCH] mock a drm_plane in igt_check_plane_state to make the test more robust Claudio Suarez
2021-12-02  9:49           ` Claudio Suarez
2021-12-02  9:51         ` [PATCH v2] drm: fix error found in some cases after the patch d1af5cd86997 Claudio Suarez
2021-12-02  9:51           ` Claudio Suarez
2021-12-20  9:18           ` Daniel Vetter
2021-12-20  9:18             ` Daniel Vetter
2021-12-20  9:18             ` Daniel Vetter
2021-12-20 17:11             ` Daniel Vetter
2021-12-20 17:11               ` Daniel Vetter
2021-12-21 22:55               ` Claudio Suarez [this message]
2021-12-21 22:55                 ` Claudio Suarez

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=YcJbXva93zJJBGbE@gineta.localdomain \
    --to=cssk@net-c.es \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.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 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.