From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Dave Airlie <airlied@linux.ie>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: linux-next: manual merge of the drm-tegra tree with the drm tree
Date: Tue, 21 Mar 2017 15:10:31 +0100 [thread overview]
Message-ID: <20170321141031.GG30407@ulmo.ba.sec> (raw)
In-Reply-To: <20170321114545.39fdd45a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On Tue, Mar 21, 2017 at 11:45:45AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drm-tegra tree got a conflict in:
>
> drivers/gpu/drm/tegra/drm.c
>
> between commit:
>
> 10437d9b475e ("drm: tegra: use vblank hooks in struct drm_crtc_funcs")
>
> from the drm tree and commit:
>
> 3f2ea8cee24f ("drm/tegra: Don't leak kernel pointer to userspace")
>
> from the drm-tegra tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Stephen,
your resolution looks good to me.
Dave,
the conflict is fairly trivial to resolve, but if you prefer I can
rebase the Tegra tree onto your -next to avoid it.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-21 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 0:45 linux-next: manual merge of the drm-tegra tree with the drm tree Stephen Rothwell
2017-03-21 14:10 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-16 1:12 Stephen Rothwell
2022-02-23 16:30 broonie
2022-02-28 3:30 ` Stephen Rothwell
2022-02-28 3:30 ` Stephen Rothwell
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=20170321141031.GG30407@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawn.guo@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.