Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp762476imm; Fri, 27 Jul 2018 05:48:24 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcYUwmvtIaAUHUZsiQ6PN9sHNr+tcT3TjOi0QSiny9TEELQkSO7s1HlkpKVeUEGWiWUjNv1 X-Received: by 2002:a62:87ce:: with SMTP id i197-v6mr6599000pfe.62.1532695704037; Fri, 27 Jul 2018 05:48:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532695704; cv=none; d=google.com; s=arc-20160816; b=CUdPpflZM8vF5beQ2omtEMBCCy6HTxQy0h8QZABM4WF5FBx/C4/izPTjeUeUyXiLlV 6VMRCyYsBBYNh21+CpTRyTCVLXNuRWvVLW8LdWYFQisBEmMEWqN3qzIl3PKVI+mRGeID 0KPU/QZ+ue9W0kw8fn1QQyOPwdbqmLfH5zvVSnBzwyOosCVVUW88XqvB7w5vBsHByYA9 Ph+RT+Cru3zv8zGiERs0DDRE6bP401YGCOsArFRBNwGbhpHxe8rONUfrDDdw0L5tqzDs bOWJG68rbTBOc9ivEmy35zxiTkD9vKs1P5EYvAG5bdH26jhPtZ9gTWopwzXOUHo2giuu Ow4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=YgPTPsndh0fyDgPXZnsG4Sn0s5ds7L5LuEHGX13wMAI=; b=E2Im4qY/cBBfbnBgqIKmyeVIbCteZHSSii1MRsH1uUtO7RGI+Igg2bpja5jSWrMB1I FmxFV/6Tj7r/vzPoH/iVt9pBlr4VCN8CNrcudk6sO8JAWN0v6ECjQsBwuxzMwP5qiK5l gzTlyVdgGCKMYuw32tZZmIYp5qlul0GtNhrjkRdzgpmnnKdI9i/PVxO3m2+cXKxGxlhb UGZ53BsQtk3KCWfhz70sEMoEn89VA8ZsWummdZBc7hLCinTsAYksYtFxjTBv3BU9YlRN SvZIfU0LuFTFVVvT8ioV05jrNQ9sys7udmNWo1gqQHm0S+7JUnoKuXrI9CaT38OD/D0o 3D0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=pW86vu2q; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a24-v6si3854032pgi.515.2018.07.27.05.48.09; Fri, 27 Jul 2018 05:48:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=pW86vu2q; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730970AbeG0OJF (ORCPT + 99 others); Fri, 27 Jul 2018 10:09:05 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:50446 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728384AbeG0OJF (ORCPT ); Fri, 27 Jul 2018 10:09:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=YgPTPsndh0fyDgPXZnsG4Sn0s5ds7L5LuEHGX13wMAI=; b=pW86vu2qZs+1AfAT5ftOFbcWa 9AU0INa/Vj0XIISSHshDp3wy2EmBdNYguHle6UZ2iEq7dtBBeEwi7wPdWcAb/U5yqeC8B5WQoWiiC 9CX4jtjpbihVpy66E4naZZq/8CSkS/Oux1k/CC+viANCI5XuV+BWf3OCANIwGW46vY59jqBXL5EBf cCquK1qp1BJzLTMPIacjtkrdH01qtAId4AVrcQSNmZvjuN2FcNBJwicg3MeTgL8PHPFYN4sWhfbRx edyB1mDYObb40dGyz1PBT8tzUEm6NlO7aaT0QuyqdkKzK320Jiw5NZ+gIHZto8eF9u4chrR6zPW0m FrT/Dkstg==; Received: from 179.176.120.227.dynamic.adsl.gvt.net.br ([179.176.120.227] helo=coco.lan) by bombadil.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1fj29L-0001ha-9u; Fri, 27 Jul 2018 12:47:15 +0000 Date: Fri, 27 Jul 2018 09:47:08 -0300 From: Mauro Carvalho Chehab To: Pavel Machek Cc: pali.rohar@gmail.com, sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, clayton@craftyguy.net, martijn@brixit.nl, sakari.ailus@linux.intel.com, Filip =?UTF-8?B?TWF0aWpldmnEhw==?= , mchehab@s-opensource.com, sakari.ailus@iki.fi, linux-media@vger.kernel.org, hans.verkuil@cisco.com Subject: Re: [PATCH, libv4l]: Make libv4l2 usable on devices with complex pipeline Message-ID: <20180727094708.18ef4e4e@coco.lan> In-Reply-To: <20180708213258.GA18217@amd> References: <20180708213258.GA18217@amd> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Sun, 8 Jul 2018 23:32:58 +0200 Pavel Machek escreveu: > Add support for opening multiple devices in v4l2_open(), and for > mapping controls between devices. > > This is necessary for complex devices, such as Nokia N900. Hi Pavel, I tried to apply it here, but it seems that there are something wrong with the patch: $ quilt push -f --merge Applying patch patches/lmml_50901_libv4l_make_libv4l2_usable_on_devices_with_complex_pipeline.patch patching file lib/include/libv4l2.h patching file lib/libv4l2/libv4l2-priv.h patching file lib/libv4l2/libv4l2.c Hunk #6 NOT MERGED at 1830-1857. misordered hunks! output would be garbled Hunk #7 FAILED at 1224. Hunk #8 NOT MERGED at 1858-2057. 1 out of 8 hunks FAILED -- saving rejects to file lib/libv4l2/libv4l2.c.rej patching file lib/libv4lconvert/control/libv4lcontrol.c Applied patch patches/lmml_50901_libv4l_make_libv4l2_usable_on_devices_with_complex_pipeline.patch (forced; needs refresh) I even tried to reset the tree to a patchset earlier than July, 8. Same issue. I could manually try to fix it, but that misordered hunks warning is weird. Makes me wonder if the patch is not mangled. Could you please re-send it on the top of upstream? Better to use git send-email, as it won't mangle your patch. Alternatively, please send me a ssh public key in private, and I'll give you access to the repository where you can store those patches. Thanks! Mauro Thanks, Mauro