Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp517472imm; Fri, 27 Jul 2018 00:59:39 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeNqS5leUEStX7ButoOyRJ9CqG+XGTllf911cR55WQVZFCkrO995tSmJcz4/zMqxfR5s9Ax X-Received: by 2002:a17:902:8308:: with SMTP id bd8-v6mr5051162plb.329.1532678379490; Fri, 27 Jul 2018 00:59:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532678379; cv=none; d=google.com; s=arc-20160816; b=yOG2CJtPFUtIL5UVyG65JQ+u7EBfqyD/n6vmkfsPMO0risseaQISsMKJyUNT/KbxTl 8NlRfHmdYpyJ+2CQWqa3aQ0WI5RxEtKPFZ4SRJd9oWT76MX5MeExMks/8lKZH+2VTdia 5JEgmLXeVED1UZKy+7hX0RPgIeUppY/Zs/ffDBOj5G3qD2dC3B4xNfUunph/6JMzmDt9 lf+2tuzEKNIy8yuTx02mASJIG2dWeuzaYMnFKE1qE2gefOauLINjA3ogoj9QVunGebip x4gP2om6LFpGvkdJc1EnW9be+N4lXvJGcMx2hqrpxhelnOL89gafuDEz298zU9dSqt1r iaxA== 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:date:cc:to:from:subject:message-id :arc-authentication-results; bh=Qj5wNnq1kzxPHUjIPpqqbQbsldB8bGnrTgitptUTdLw=; b=QGec1IPkuu/r791ksgARZdYM5nZqIail7lw/EpoXbdcMI8ryyHO1W2KCbYRQ1lqp+/ h7JxDKoMyuqxZM4QKRgbFptMUXnv3ktwG0n/cNL/w9pO0c2VF6PYN7HDZQ1mS4mkyZWY WPzpXHjH6nwq9tDw5iIVOm/2ocT1RQxxOG8xvWvcsd7Ps+vRjLc52upJX5rm6jmahaYq 11Y0WTWPHtJ+uw8O//Vkl6jQkEsuaYkjPKNie1Mag3V0gfU60GnPusLXDDHAWdjz8MB1 UTv7wvrdn9kj9kCYU8/R4vVe9v/V6wJckmJdCEjDf86S0+584GAoTpcNmqJZg7hDMmwB uK7Q== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a9-v6si3335446pgn.177.2018.07.27.00.59.24; Fri, 27 Jul 2018 00:59:39 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730088AbeG0JSd (ORCPT + 99 others); Fri, 27 Jul 2018 05:18:33 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:46717 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729536AbeG0JSc (ORCPT ); Fri, 27 Jul 2018 05:18:32 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1fixdA-0000hX-2w; Fri, 27 Jul 2018 09:57:44 +0200 Message-ID: <1532678263.4694.4.camel@pengutronix.de> Subject: Re: linux-next: manual merge of the drm tree with the v4l-dvb tree From: Philipp Zabel To: Stephen Rothwell , Dave Airlie , DRI , Mauro Carvalho Chehab Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Steve Longerbeam Date: Fri, 27 Jul 2018 09:57:43 +0200 In-Reply-To: <20180727143640.4dc3fa54@canb.auug.org.au> References: <20180727143640.4dc3fa54@canb.auug.org.au> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2018-07-27 at 14:36 +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drm tree got a conflict in: > > drivers/gpu/ipu-v3/ipu-cpmem.c > > between commit: > > 343b23a7c6b6 ("media: gpu: ipu-v3: Allow negative offsets for interlaced scanning") > > from the v4l-dvb tree and commit: > > 4e3c5d7e05be ("gpu: ipu-v3: Allow negative offsets for interlaced scanning") > > from the drm tree. > > I fixed it up (I just used the drm tree version) This is correct. > and can carry the fix > as necessary. This is now fixed as far as linux-next is concerned, but > any non trivial conflicts should be mentioned to your upstream maintainer > when your tree is submitted for merging. You may also want to consider > cooperating with the maintainer of the conflicting tree to minimise any > particularly complex conflicts. Steve had pointed out a valid issue with 343b23a7c6b6, I didn't expect this patch to get picked up. I should have mentioned on linux-media that I had submitted the fixed version for inclusion in drm-next. regards Philipp