From: Chun-Kuang Hu <chunkuang.hu@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Jitao Shi <jitao.shi@mediatek.com>,
David Airlie <airlied@linux.ie>, Bernard Zhao <bernard@vivo.com>,
YueHaibing <yuehaibing@huawei.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Daniel Vetter <daniel@ffwll.ch>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Anand K Mistry <amistry@chromium.org>
Subject: Re: [GIT PULL v2] mediatek drm next for 5.8
Date: Thu, 21 May 2020 23:55:31 +0800 [thread overview]
Message-ID: <CAAOTY__9bnTkQd5VFemrK3bVDMzf6AttssuZgXecO+_t9MMmaA@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tzqQ5G82mSACX5speUF2j-8vz7SrOcj7XLsKCjhe3GT6A@mail.gmail.com>
Hi, Dave:
Dave Airlie <airlied@gmail.com> 於 2020年5月20日 週三 下午1:47寫道:
>
> On Wed, 20 May 2020 at 15:44, Dave Airlie <airlied@gmail.com> wrote:
> >
> > On Mon, 18 May 2020 at 10:06, Chun-Kuang Hu <chunkuang.hu@kernel.org> wrote:
> > >
> > > Hi, Dave & Daniel:
> > >
> > > This include dpi pin mode swap, config mipi_tx current and impedance,
> > > and some fixup. I drop drm_bridge patches in this version.
> > >
> > > The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
> > > Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
> > > are available in the Git repository at:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git
> > > tags/mediatek-drm-next-5.8
> > > for you to fetch changes up to 007d274a017bb4e2ef7b922c2f54f40cf2073664:
> >
> > Did you edit this by hand or pass it through some mailserver that
> > chewed it up, I had to reconstruct this pull from the above bits, I've
> > no idea why it's so messed up in the first place.
>
> and why does it contain an unexplained backmerge?
>
> Merge tag 'v5.7-next-drm-stable' of
> ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux
> into mediatek-drm-next
>
> Please don't ever backmerge fixes into next pull, without a long
> explaination or if you really need it ask us first,
>
> Please resend this again cleaned up.
OK, to make things easier, I just resend and cleaned up.
If one day I need a backmerge fixes, I would ask you first.
Regards,
Chun-Kuang.
>
> Dave.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-05-21 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 0:06 [GIT PULL v2] mediatek drm next for 5.8 Chun-Kuang Hu
2020-05-20 5:44 ` Dave Airlie
2020-05-20 5:46 ` Dave Airlie
2020-05-21 15:55 ` Chun-Kuang Hu [this message]
2020-05-22 15:58 ` Matthias Brugger
2020-05-28 6:01 ` Dave Airlie
2020-05-21 15:52 ` Chun-Kuang Hu
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=CAAOTY__9bnTkQd5VFemrK3bVDMzf6AttssuZgXecO+_t9MMmaA@mail.gmail.com \
--to=chunkuang.hu@kernel.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=amistry@chromium.org \
--cc=bernard@vivo.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=enric.balletbo@collabora.com \
--cc=hsinyi@chromium.org \
--cc=jitao.shi@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).