[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6A617A27-DBE8-4537-A122-6ACA98B8A6B4@micronovasrl.com>
Date: Tue, 28 Nov 2017 14:03:43 +0100
From: Giulio Benetti <giulio.benetti@...ronovasrl.com>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Thomas van Kleef <thomas@...sch.nl>,
Hans Verkuil <hverkuil@...all.nl>,
Andreas Baierl <list@...reisrum.de>,
linux-sunxi <linux-sunxi@...glegroups.com>,
linux@...linux.org.uk, wens@...e.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org
Subject: Re: [linux-sunxi] Cedrus driver
Hi,
> Il giorno 28 nov 2017, alle ore 13:52, Maxime Ripard <maxime.ripard@...e-electrons.com> ha scritto:
>
> On Tue, Nov 28, 2017 at 12:54:08PM +0100, Giulio Benetti wrote:
>>>>> Should I be working in sunxi-next I wonder?
>>>>
>>>> Yes, this is the best way, cedrus is very specific to sunxi.
>>>> So before working on mainline, I think the best is to work un sunxi-next branch.
>>>
>>> Is the requests2 api in sunxi-next?
>>
>> It should be there,
>> take a look at latest commit of yesterday:
>> https://github.com/linux-sunxi/linux-sunxi/commit/df7cacd062cd84c551d7e72f15b1af6d71abc198
>
> No, it shouldn't. sunxi-next is about patches that are related to
> sunxi that have been accepted in their respective maintainers'
> branches.
>
> While we could argue about the first criteria, the second one is not
> respected.
>
> And really, just develop against 4.14. sunxi-next is rebased, and it's
> just not something you can base some work on.
Where do we can work on then?
Should Thomas setup his own github repo?
What about the one you’ve set up @free-electrons?
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
Powered by blists - more mailing lists