All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
	David Airlie <airlied@linux.ie>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/scheduler: make unexported items static
Date: Fri, 11 Oct 2019 09:07:44 -0400	[thread overview]
Message-ID: <CADnq5_PnCak2gVQSC-WK-Hs=+RorTr__Z3Lqu5MfhP_YJZe00g@mail.gmail.com> (raw)
In-Reply-To: <6f09197a-d266-aa00-47b8-dd3deede59c9@codethink.co.uk>

Already applied.  thanks.

Alex

On Fri, Oct 11, 2019 at 2:48 AM Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>
> On 09/10/2019 13:14, Ben Dooks wrote:
> > The drm_sched_fence_ops_{scheduled,finished} are not exported
> > from the file so make them static to avoid the following
> > warnings from sparse:
> >
> > drivers/gpu/drm/scheduler/sched_fence.c:131:28: warning: symbol 'drm_sched_fence_ops_scheduled' was not declared. Should it be static?
> > drivers/gpu/drm/scheduler/sched_fence.c:137:28: warning: symbol 'drm_sched_fence_ops_finished' was not declared. Should it be static?
> >
> > Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>
> If it is useful I can get these into a public git repo and send
> a pull request.
>
> --
> Ben Dooks                               http://www.codethink.co.uk/
> Senior Engineer                         Codethink - Providing Genius
>
> https://www.codethink.co.uk/privacy.html
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-10-11 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 12:14 [PATCH] drm/scheduler: make unexported items static Ben Dooks
2019-10-10  7:54 ` Ben Dooks
2019-10-11 13:07   ` Alex Deucher [this message]
2019-10-10 14:18 ` Alex Deucher

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='CADnq5_PnCak2gVQSC-WK-Hs=+RorTr__Z3Lqu5MfhP_YJZe00g@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=airlied@linux.ie \
    --cc=ben.dooks@codethink.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@lists.codethink.co.uk \
    /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.