linux-kernel - Re: linux-next: please clean up the clockevents 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] [day] [month] [year] [list]

Message-ID: <bcd7f298-c223-0d40-dbf5-edc8e1650794@linaro.org>
Date:   Thu, 20 Dec 2018 09:47:53 +0100
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: please clean up the clockevents tree

On 20/12/2018 06:15, Stephen Rothwell wrote:
> Hi Daniel,
> 
> It looks like all the changes in the clockevents tree appear as other
> commits in other tree(s).  Could you please reset your tree to somewhere
> in your upstream tree as it is beginning to produce conflicts.

Done.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog