On Tue, Jan 03, 2017 at 08:53:54AM +0800, Qu Wenruo wrote:
>
>
> At 01/03/2017 12:47 AM, David Sterba wrote:
> > On Fri, Dec 30, 2016 at 09:00:36AM +0800, Qu Wenruo wrote:
> >> Hi, please fetch the following branch for next branch:
> >> https://github.com/adam900710/linux.git fujitsu_for_next
>
At 01/03/2017 12:47 AM, David Sterba wrote:
On Fri, Dec 30, 2016 at 09:00:36AM +0800, Qu Wenruo wrote:
Hi, please fetch the following branch for next branch:
https://github.com/adam900710/linux.git fujitsu_for_next
This branch contains most of Fujitsu unmerged patches for for-next branch.
On Mon, Jan 02, 2017 at 05:47:38PM +0100, David Sterba wrote:
> On Fri, Dec 30, 2016 at 09:00:36AM +0800, Qu Wenruo wrote:
> > Hi, please fetch the following branch for next branch:
> > https://github.com/adam900710/linux.git fujitsu_for_next
> >
> > This branch contains most of Fujitsu unmerged
On Fri, Dec 30, 2016 at 09:00:36AM +0800, Qu Wenruo wrote:
> Hi, please fetch the following branch for next branch:
> https://github.com/adam900710/linux.git fujitsu_for_next
>
> This branch contains most of Fujitsu unmerged patches for for-next branch.
>
> Latest David's for-next-20161219
Hi, please fetch the following branch for next branch:
https://github.com/adam900710/linux.git fujitsu_for_next
This branch contains most of Fujitsu unmerged patches for for-next branch.
Latest David's for-next-20161219 branch can cause kernel panic so I don't
use it as base, but v4.10-rc1.
I