linux-kernel - Re: linux-next: build failure after merge of the s5p tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFzuEP7poPj_TiC28+T7Xn-6G1Lydt=q5FMVTj_XhOVf3w@mail.gmail.com>
Date:	Tue, 3 Jan 2012 08:20:20 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Kukjin Kim <kgene.kim@...sung.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>
Subject: Re: linux-next: build failure after merge of the s5p tree

On Tue, Jan 3, 2012 at 12:12 AM, Kukjin Kim <kgene.kim@...sung.com> wrote:
>
> OK, I see. Firstly, I will rebase my for-next as per your suggestion. As you
> know, I just wanted to avoid known conflicts with driver-core tree.

Please, in general you should *not* rebase on top of other peoples
trees either. What's the conflict and why do you need that other tree
in the first place?

                       Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/