From: Behan Webster <behanw@converseincode.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
llvmlinux@lists.linuxfoundation.org,
Wim Van Sebroeck <wim@iguana.be>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Charlebois <charlebm@gmail.com>,
Rob Clark <robdclark@gmail.com>
Subject: Re: linux-next: manual merge of the llvmlinux tree with the tree
Date: Mon, 15 Sep 2014 07:24:28 -0700 [thread overview]
Message-ID: <5416F69C.8040905@converseincode.com> (raw)
In-Reply-To: <20140915163813.490886b4@canb.auug.org.au>
On 09/14/14 23:38, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the llvmlinux tree got a conflict in
> drivers/gpu/drm/msm/hdmi/hdmi.c between commit fc886107c556 ("drm/msm:
> Change nested function to static function") from the watchdog tree and
> commit 8f2c494adad0 ("msm, hdmi: LLVMLinux: Remove nested function from
> HDMI driver") from the llvmlinux tree.
>
> I fixed it up (these patches are doing the same thing, so I used the
> version in the watchdog tree) and can carry the fix as necessary (no
> action is required).
>
> P.S. Behan, I noticed that the llvmlinux patch has no Signed-off-by
> from you even though you committed it ...
Drat. That patch wasn't supposed to be in there. Sorry about that.
Yeah. That one was accepted upstream already. I was carrying it in my
repos so we could still build until it made it to mainline. I should not
have put that in linux-next. I actually just had to pull it out of my
own builds due to the same merge issue.
Hmm. Seems I put a couple of patches into the for-next branch late last
night which shouldn't have been. Fixed.
Apologies,
Behan
--
Behan Webster
behanw@converseincode.com
prev parent reply other threads:[~2014-09-15 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 6:38 linux-next: manual merge of the llvmlinux tree with the tree Stephen Rothwell
2014-09-15 6:38 ` Stephen Rothwell
2014-09-15 14:24 ` Behan Webster [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=5416F69C.8040905@converseincode.com \
--to=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=robdclark@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=wim@iguana.be \
/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.