All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Mars Cheng <mars.cheng@mediatek.com>,
	Bibby Hsieh <bibby.hsieh@mediatek.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] soc: mediatek: updates for v5.6
Date: Fri, 17 Jan 2020 11:22:50 -0800	[thread overview]
Message-ID: <CAOesGMgFXQzHRQVQNwZU7-jO=eqWT5Dv82RRicMP-dKXwbTfvA@mail.gmail.com> (raw)
In-Reply-To: <9b365e76-e346-f813-d750-d7cfd0d16e4e@gmail.com>

Hi,

On Mon, Jan 13, 2020 at 2:18 AM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>
> Hi Olof,
> Hi ARnds,
>
> Please have a look on the following patches for mediatek soc drivers for v5.6
>
> I includes the stable branch v5.5-next/cmdq-stable which should also be merged
> in the DRM tree. I'm not very familiar with providing a stable tree, although I
> double-checked that in the pull request to the DRM tree the commit IDs are the
> same, I thought it is worth noting.

I'm a little confused as to how the dependencies are expected to line up here.

Does your non-DRM contents rely on the DRM pieces? If so, you need
them to be based on top of that branch to make sure they are
bisectable, not merge the DRM branch in on top (since a bisect might
land on a commit before the merge).

But... I also don't see how there's any actual dependency here? There
are a few cleanups, the DRM branch builds without them, and the branch
when checked out right before the DRM merge in your pull request, also
builds.


-Olof

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

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Mars Cheng <mars.cheng@mediatek.com>,
	Bibby Hsieh <bibby.hsieh@mediatek.com>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] soc: mediatek: updates for v5.6
Date: Fri, 17 Jan 2020 11:22:50 -0800	[thread overview]
Message-ID: <CAOesGMgFXQzHRQVQNwZU7-jO=eqWT5Dv82RRicMP-dKXwbTfvA@mail.gmail.com> (raw)
In-Reply-To: <9b365e76-e346-f813-d750-d7cfd0d16e4e@gmail.com>

Hi,

On Mon, Jan 13, 2020 at 2:18 AM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>
> Hi Olof,
> Hi ARnds,
>
> Please have a look on the following patches for mediatek soc drivers for v5.6
>
> I includes the stable branch v5.5-next/cmdq-stable which should also be merged
> in the DRM tree. I'm not very familiar with providing a stable tree, although I
> double-checked that in the pull request to the DRM tree the commit IDs are the
> same, I thought it is worth noting.

I'm a little confused as to how the dependencies are expected to line up here.

Does your non-DRM contents rely on the DRM pieces? If so, you need
them to be based on top of that branch to make sure they are
bisectable, not merge the DRM branch in on top (since a bisect might
land on a commit before the merge).

But... I also don't see how there's any actual dependency here? There
are a few cleanups, the DRM branch builds without them, and the branch
when checked out right before the DRM merge in your pull request, also
builds.


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-01-17 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:17 [GIT PULL] soc: mediatek: updates for v5.6 Matthias Brugger
2020-01-13 10:17 ` Matthias Brugger
2020-01-17 19:22 ` Olof Johansson [this message]
2020-01-17 19:22   ` Olof Johansson
2020-01-17 21:52   ` Matthias Brugger
2020-01-17 21:52     ` Matthias Brugger
2020-01-20 19:25     ` Olof Johansson
2020-01-20 19:25       ` Olof Johansson

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='CAOesGMgFXQzHRQVQNwZU7-jO=eqWT5Dv82RRicMP-dKXwbTfvA@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=bibby.hsieh@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mars.cheng@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=soc@kernel.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.