All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Xinliang Liu <xinliang.liu@linaro.org>
Cc: Peter Griffin <peter.griffin@linaro.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Guodong Xu <guodong.xu@linaro.org>
Subject: Re: [GIT PULL] drm-hisilicon-next
Date: Wed, 30 Aug 2017 09:41:51 +0200	[thread overview]
Message-ID: <20170830074151.opgvu5ridmdpwtx5@phenom.ffwll.local> (raw)
In-Reply-To: <CAGd==06WJHnbtv9nHiVonHVnsX_2Bp7WceX80_VySXi6HjQWhQ@mail.gmail.com>

On Wed, Aug 30, 2017 at 01:57:35PM +0800, Xinliang Liu wrote:
> On 29 August 2017 at 21:57, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Tue, Aug 29, 2017 at 11:54 AM, Xinliang Liu <xinliang.liu@linaro.org> wrote:
> >> Hi Dave,
> >>
> >> On 29 August 2017 at 16:32, Daniel Vetter <daniel@ffwll.ch> wrote:
> >>> On Tue, Aug 29, 2017 at 10:46:33AM +0800, Xinliang Liu wrote:
> >>>> Hi Dave,
> >>>> One fix for next.
> >>>> Sorry for late pull request. If it can't catch this round, will resend
> >>>> on next round.
> >>>
> >>> drm-misc is always open for features, which makes this a lot simpler. Just
> >>> in case you want to reconsider moving hisilicon into drm-misc :-)
> >>
> >> If  moving hisilicon into drm-misc make things simpler, I would like to do it.
> >> Just clarify how to do this:
> >> I just need to change the git tree to drm-misc? I see a lot of drm
> >> drivers maintainers set the their git tree to
> >> git://anongit.freedesktop.org/drm/drm-misc.
> >> The means to be an drm-misc maintainer, right?
> >> I wonder how new driver specific features/fixes patches go into drm-misc then?
> >>  Do I need to send a pull request to  drm-misc tree. I don't think I
> >> have a write permission to drm-misc tree.
> >
> > You'll need to become drm-misc committer, and patches are pushed
> > directly using the scripts we have:
> >
> > https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html
> >
> > Here's the rules for how drm-misc works:
> >
> > https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
> >
> > drm-misc is essentially a service provided to take care of some of the
> > maintainer chores, but review and patch merging still needs to be done
> > by the individual driver owners (i.e. we won't take a new driver
> > without a committer for it).
> 
> Thanks Daniel,
> We are considering  switch to a stable maintainer for hisilicon.
> After that we will move hisilicon to drm-misc.

You can also have a team (2 people or so) if you want.
-Daniel

> 
> Best,
> Xinliang
> 
> 
> >
> > Cheers, Daniel
> >
> >>
> >> Best,
> >> Xinliang
> >>
> >>> -Daniel
> >>>
> >>>>
> >>>>
> >>>> Best,
> >>>> Xinliang
> >>>>
> >>>>
> >>>> The following changes since commit 7846b12fe0b5feab5446d892f41b5140c1419109:
> >>>>
> >>>>   Merge branch 'drm-vmwgfx-next' of
> >>>> git://people.freedesktop.org/~syeh/repos_linux into drm-next
> >>>> (2017-08-29 10:38:14 +1000)
> >>>>
> >>>> are available in the git repository at:
> >>>>
> >>>>
> >>>>   git@github.com:xin3liang/linux.git tags/drm-hisilicon-next-2017-08-29
> >>>>
> >>>> for you to fetch changes up to 834fe0f6023a4fad68612dbbe93866c4df32142e:
> >>>>
> >>>>   drm/hisilicon: Ensure LDI regs are properly configured. (2017-08-29
> >>>> 10:17:18 +0800)
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> hisilicon-drm-next
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Peter Griffin (1):
> >>>>       drm/hisilicon: Ensure LDI regs are properly configured.
> >>>>
> >>>>  drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 3 +++
> >>>>  1 file changed, 3 insertions(+)
> >>>> _______________________________________________
> >>>> dri-devel mailing list
> >>>> dri-devel@lists.freedesktop.org
> >>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >>>
> >>> --
> >>> Daniel Vetter
> >>> Software Engineer, Intel Corporation
> >>> http://blog.ffwll.ch
> >
> >
> >
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > +41 (0) 79 365 57 48 - http://blog.ffwll.ch

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-08-30  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  2:46 [GIT PULL] drm-hisilicon-next Xinliang Liu
2017-08-29  8:32 ` Daniel Vetter
2017-08-29  9:54   ` Xinliang Liu
2017-08-29 13:57     ` Daniel Vetter
2017-08-30  5:57       ` Xinliang Liu
2017-08-30  7:41         ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-01  2:51 Xinliang Liu
2016-07-04 11:09 Xinliang Liu

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=20170830074151.opgvu5ridmdpwtx5@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guodong.xu@linaro.org \
    --cc=peter.griffin@linaro.org \
    --cc=xinliang.liu@linaro.org \
    /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.