From: Inki Dae <inki.dae@samsung•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Dave Airlie <airlied@linux•ie>
Subject: Re: linux-next: rebase of the drm-exynos tree
Date: Tue, 18 Aug 2015 10:21:32 +0900 [thread overview]
Message-ID: <55D2889C.20404@samsung.com> (raw)
In-Reply-To: <20150818085050.7a38f4ef@canb.auug.org.au>
Hi Stephen,
On 2015년 08월 18일 07:50, Stephen Rothwell wrote:
> Hi Inki,
>
> I noticed today that your tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#exynos-drm/for-next)
> has been merged by Dave into his drm tree. Unfortunately, your tree
> has also been rebased onto Linus's v4.2-rc7. So now the commits
> 0cb600d9be30-f8f66412fa6c in your tree are duplicated of commits
> d36b3004ca2c-2a8cb4894540 in Dave's. Please tidy this up (i.e. your
> exynos-drm/for-next branch should be commit 2a8cb4894540 or something
> later in Dave's tree) and you should continue your work from there.
Right, I had requested git-pull. Will do re-base on top of Dave's tree.
Thanks,
Inki Dae
>
prev parent reply other threads:[~2015-08-18 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 22:50 linux-next: rebase of the drm-exynos tree Stephen Rothwell
2015-08-18 1:21 ` Inki Dae [this message]
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=55D2889C.20404@samsung.com \
--to=inki.dae@samsung$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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