Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754133AbdFMVJM (ORCPT ); Tue, 13 Jun 2017 17:09:12 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:40566 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753875AbdFMVJC (ORCPT ); Tue, 13 Jun 2017 17:09:02 -0400 Date: Tue, 13 Jun 2017 23:09:00 +0200 From: Pavel Machek To: Sakari Ailus Cc: Laurent Pinchart , mchehab@kernel.org, kernel list , ivo.g.dimitrov.75@gmail.com, sre@kernel.org, pali.rohar@gmail.com, linux-media@vger.kernel.org Subject: Re: v4l2-fwnode: status, plans for merge, any branch to merge against? Message-ID: <20170613210900.GA31456@amd> References: <2414221.XNA4JCFMRx@avalon> <20170302090143.GB27818@amd> <20170302101603.GE27818@amd> <20170302112401.GF3220@valkosipuli.retiisi.org.uk> <20170302123848.GA28230@amd> <20170304130318.GU3220@valkosipuli.retiisi.org.uk> <20170306072323.GA23509@amd> <20170310225418.GJ3220@valkosipuli.retiisi.org.uk> <20170613122240.GA2803@amd> <20170613124748.GD12407@valkosipuli.retiisi.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <20170613124748.GD12407@valkosipuli.retiisi.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1391 Lines: 50 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > Are there any news about the fwnode branch? > >=20 > > I have quite usable camera, but it is still based on > > 982e8e40390d26430ef106fede41594139a4111c (that's v4.10). It would be > > good to see fwnode stuff upstream... are there any plans for that? > >=20 > > Is there stable branch to which I could move the stuff? >=20 > What's relevant for most V4L2 drivers is in linux-media right now. >=20 > There are new features that will take some time to get in. The trouble has > been, and continue to be, that the patches need to go through various tre= es > so it'll take some time for them to be merged. >=20 > I expect to have most of them in during the next merge window. So git://linuxtv.org/media_tree.git branch master is the right one to work one? Thanks, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllAVGwACgkQMOfwapXb+vL1ggCeLv9R21D653EHUH0xuS7PRI6T 3IAAoJAso+qOcDdCuIPbCqyoZDKLgYNE =8M7z -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--