dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <sean@poorly.run>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <seanpaul@chromium.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Sean Paul <sean@poorly.run>
Subject: Re: [PATCH 1/2] drm: Fix duplicate const warning in drm_gem_ttm_helper.c
Date: Mon, 23 Sep 2019 09:40:09 -0400	[thread overview]
Message-ID: <20190923134009.GY218215@art_vandelay> (raw)
In-Reply-To: <20190923065929.4dcs7k6sb63ueyax@sirius.home.kraxel.org>

On Mon, Sep 23, 2019 at 08:59:29AM +0200, Gerd Hoffmann wrote:
> On Fri, Sep 20, 2019 at 03:35:51PM -0400, Sean Paul wrote:
> > From: Sean Paul <seanpaul@chromium.org>
> > 
> > For the warning
> > ../drivers/gpu/drm/drm_gem_ttm_helper.c:26:20: warning: duplicate ‘const’ declaration specifier [-Wduplicate-decl-specifier]
> 
> I have a drm_print_bits patch in flight which fixes this too (Cc'ed you
> on v2).

Ah neat, thanks.

Sean

> 
> cheers,
>   Gerd
> 

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-09-23 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 19:35 [PATCH 1/2] drm: Fix duplicate const warning in drm_gem_ttm_helper.c Sean Paul
2019-09-20 19:35 ` [PATCH 2/2] Documentation/gpu: Fix no structured comments warning for drm_gem_ttm_helper.h Sean Paul
2019-09-23  6:59   ` Gerd Hoffmann
2019-09-23 14:08     ` Sean Paul
2019-09-23  7:03   ` Thomas Zimmermann
2019-10-08 16:36     ` Daniel Vetter
2019-09-23  6:57 ` [PATCH 1/2] drm: Fix duplicate const warning in drm_gem_ttm_helper.c Thomas Zimmermann
2019-09-23  6:59 ` Gerd Hoffmann
2019-09-23 13:40   ` Sean Paul [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=20190923134009.GY218215@art_vandelay \
    --to=sean@poorly.run \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=seanpaul@chromium.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