public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: CK Hu <ck.hu@mediatek.com>
To: Dave Airlie <airlied@gmail.com>
Cc: ryder.lee@mediatek.com, linux-mediatek@lists.infradead.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	chunhui.dai@mediatek.com
Subject: Re: [GIT PULL] mediatek drm next for 4.20
Date: Thu, 11 Oct 2018 14:21:19 +0800	[thread overview]
Message-ID: <1539238879.9926.3.camel@mtksdaap41> (raw)
In-Reply-To: <CAPM=9tzr2f+=iyZb0yPjjABNiehRqL4xEQMqirr__qaPgu-T6w@mail.gmail.com>

Hi, Dave:

On Thu, 2018-10-11 at 13:56 +1000, Dave Airlie wrote:
> On Thu, 11 Oct 2018 at 12:29, CK Hu <ck.hu@mediatek.com> wrote:
> >
> > Hi, Dave:
> >
> > On Thu, 2018-10-11 at 11:42 +1000, Dave Airlie wrote:
> > > On Thu, 11 Oct 2018 at 11:25, CK Hu <ck.hu@mediatek.com> wrote:
> > > >
> > > > Hi, Dave:
> > > >
> > > > Ping this. If there is any problem, tell me and I would fix it.
> > > >
> > > > Regards,
> > > > CK
> > > >
> > > > On Thu, 2018-10-04 at 09:22 +0800, CK Hu wrote:
> > > > > Hi, Dave:
> > > > >
> > > > > This include hdmi output support for mt2701 and mt7623.
> > > > >
> > > > > Regards,
> > > > > CK
> > > > >
> > > > > The following changes since commit
> > > > > 87c2ee740c07f1edae9eec8bc45cb9b32a68f323:
> > > > >
> > > > >   Merge branch 'drm-next-4.20' of
> > > > > git://people.freedesktop.org/~agd5f/linux into drm-next (2018-09-28
> > > > > 09:48:40 +1000)
> > > > >
> > > > > are available in the git repository at:
> > > > >
> > > > >
> > > > >   https://github.com/ckhu-mediatek/linux.git-tags.git
> > > > > mediatek-drm-next-4.20
> > >
> > > This has two newlines which might suggest and older version of git was
> > > being used.
> >
> > I'll take care of the newline part in future. But I don't understand
> > what is the problem of older version of git? Maybe I could prevent this
> > next time.
> 
> In the recent hisilicon-next pulls Xinliang Liu mentioned the double
> lines are from git 1.9.1, and were fixed in a later version.

Yes, this request is generated by git 1.9.1. I try with git 2.15.5 and
it has no this problem. I will generate pull request by a later version.

Regards,
CK

> 
> Dave.
> 
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-10-11  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04  1:22 [GIT PULL] mediatek drm next for 4.20 CK Hu
2018-10-11  1:25 ` CK Hu
2018-10-11  1:42   ` Dave Airlie
     [not found]     ` <CAPM=9tyeONZ3Kft6_S9CNU98_ORNQ6WnV_20tDwqHTydWsQoRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-11  2:29       ` CK Hu
2018-10-11  3:56         ` Dave Airlie
2018-10-11  6:21           ` CK Hu [this message]
2018-10-11  8:21             ` Daniel Vetter

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=1539238879.9926.3.camel@mtksdaap41 \
    --to=ck.hu@mediatek.com \
    --cc=airlied@gmail.com \
    --cc=chunhui.dai@mediatek.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=ryder.lee@mediatek.com \
    /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