From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Giulio Benetti <giulio.benetti@micronovasrl.com>
Cc: Thomas van Kleef <thomas@vitsch.nl>,
Hans Verkuil <hverkuil@xs4all.nl>,
Andreas Baierl <list@imkreisrum.de>,
linux-sunxi <linux-sunxi@googlegroups.com>,
linux@armlinux.org.uk, wens@csie.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [linux-sunxi] Cedrus driver
Date: Tue, 28 Nov 2017 16:17:40 +0100 [thread overview]
Message-ID: <20171128151740.eyke3i4nuprconwf@flea.home> (raw)
In-Reply-To: <d2f659ed-1750-2859-7b43-0a4780bd3343@micronovasrl.com>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On Tue, Nov 28, 2017 at 02:12:31PM +0100, Giulio Benetti wrote:
> > > > 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?
> >
> > I already said that, please make pull requests to that repo.
>
> Sorry I can't understand which repo,
> do you mean https://github.com/free-electrons/linux-cedrus?
Yes.
> And sorry for dumb question,
> but which branch do I have to use if I want to develop a project with sunxi?
> Directly mainline patched with sunxi-next branch,
> or another branch @linux-sunxi?
Use 4.14.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-28 15:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1510059543-7064-1-git-send-email-giulio.benetti@micronovasrl.com>
[not found] ` <1b12fa21-bfe6-9ba7-ae1d-8131ac6f4668@micronovasrl.com>
[not found] ` <6fcdc0d9-d0f8-785a-bb00-b1b41c684e59@imkreisrum.de>
[not found] ` <693e8786-af83-9d77-0fd4-50fa1f6a135f@micronovasrl.com>
2017-11-16 11:02 ` [linux-sunxi] Cedrus driver Maxime Ripard
2017-11-16 12:30 ` Giulio Benetti
2017-11-16 12:53 ` Maxime Ripard
2017-11-16 12:57 ` Giulio Benetti
2017-11-16 13:12 ` Hans Verkuil
2017-11-16 13:17 ` Giulio Benetti
2017-11-16 13:39 ` Maxime Ripard
2017-11-16 13:42 ` Giulio Benetti
2017-11-28 0:03 ` Giulio Benetti
2017-11-28 8:35 ` Maxime Ripard
2017-11-28 9:50 ` Giulio Benetti
2017-11-28 11:20 ` Thomas van Kleef
2017-11-28 11:26 ` Giulio Benetti
2017-11-28 11:29 ` Thomas van Kleef
2017-11-28 11:54 ` Giulio Benetti
2017-11-28 12:31 ` Thomas van Kleef
2017-11-28 12:52 ` Maxime Ripard
2017-11-28 13:03 ` Giulio Benetti
2017-11-28 13:07 ` Maxime Ripard
2017-11-28 13:12 ` Giulio Benetti
2017-11-28 15:17 ` Maxime Ripard [this message]
2017-11-28 15:19 ` Giulio Benetti
2017-11-28 12:26 ` Maxime Ripard
2017-11-28 14:51 ` Thomas van Kleef
2017-11-28 15:35 ` Maxime Ripard
2017-11-29 15:36 ` Thomas van Kleef
2017-11-30 15:24 ` Maxime Ripard
2017-11-16 13:39 ` Hans Verkuil
2017-11-16 19:59 ` Nicolas Dufresne
2017-11-17 8:01 ` Maxime Ripard
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=20171128151740.eyke3i4nuprconwf@flea.home \
--to=maxime.ripard@free-electrons.com \
--cc=giulio.benetti@micronovasrl.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=list@imkreisrum.de \
--cc=thomas@vitsch.nl \
--cc=wens@csie.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).