Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp6560801ybi; Sun, 21 Jul 2019 21:00:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqyuTk7pp/rJrZQiT8QMoH5WYPg2kFMucVd84dQT424B6XH9vrGF8nwNZnHnn6nbJgiFs8Dm X-Received: by 2002:a63:5920:: with SMTP id n32mr67192858pgb.352.1563768048582; Sun, 21 Jul 2019 21:00:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563768048; cv=none; d=google.com; s=arc-20160816; b=g+MwQn7IVISu2yeIcdwe2a9eiIiKGOaazHVwsEZ8lPDkM6fbj72JM3AA52XKTXCex7 cRGds/2vE4soy4rj2uQjBNzPVODZpdKBvqROLahKwRDZNWnHVl+tDxdq/qpqC+8Dov+0 6L+WpsUvOE6ZkAzlo3aJZ13Iy29uYMzIxnhDCqesDNWNMxE6sbzbm2xXlmoDaHGATO2m zTy77W3iKmcsXrO0zFY55lknhsr6WGQYskTUg450n4u67qC8tdTm1k1MBOZ8MSfJiHE7 0yE/oefho9I5auYSP6b5emSUqoAFltNsol3w8nQPjdFHWd7Ur6X/fs+4D1nlCzXbt4sH OyEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=BoTOo2Q0hAaQhRV9S4lq8HdMSQdYs79oTvCprCzExNE=; b=MPpS+eTjVBgYtPyOWAvL7XMZqbHxwUvHtm00MPIYpy+ZOQbkAkp2VhAsJeYz6Iig5E sp67TiCwnDc7hMuzUaz+bW9UxqftLoK38lXafuprdlqUs9DtKYlyk+5RbPKikoaadhcS C64GdZ2kwDmpYbh81x+rtPrsYvII8/dSePWrrAQopE4mAH2LXz/4mNfkw+p/O8gj48Sz S2+rbKRXNTLgJMDmMphRXL6y1SsviqMsvBmPGrPAhK5s+RVlS7PKS+cwbmGnTniWzDYw tUyKpRtcIqAH9m8Wb1UjrT0BBHzyOiWPeUw6SrcXwPEK3kjoDoZcQBPRox4b5vDJRD9z vdhA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lixom-net.20150623.gappssmtp.com header.s=20150623 header.b="vVp/xUv+"; 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 ay3si8286870plb.174.2019.07.21.21.00.18; Sun, 21 Jul 2019 21:00:48 -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=pass header.i=@lixom-net.20150623.gappssmtp.com header.s=20150623 header.b="vVp/xUv+"; 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 S1727608AbfGVDMt (ORCPT + 99 others); Sun, 21 Jul 2019 23:12:49 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:45647 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726106AbfGVDMt (ORCPT ); Sun, 21 Jul 2019 23:12:49 -0400 Received: by mail-lf1-f68.google.com with SMTP id u10so25457646lfm.12 for ; Sun, 21 Jul 2019 20:12:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=BoTOo2Q0hAaQhRV9S4lq8HdMSQdYs79oTvCprCzExNE=; b=vVp/xUv+CtFzcPuAXowYe8wJhVlGxEwlkPGxO9uVGvr6WeSnEwgVsW6GAow0S9juzs ai84cJL7ajD0+curTRmYC7lrWpicyEyd7Y4L3et7J1JmbfOXBkO+2kB7bhI9RMs3KR0e h1+h/FM36KmpJoewzbcIMlKLQ/wjuoD/IAUUKgW1l55z3lLxy2Rh8FFQ46HuXy66nnmW xF3U+cRwtK3tCNe1xQBvm1pILf/LQDvGi3CE4wiN/M57evG0vHGSCeWaC9g9rHZa6b8N vV5llWLCjRZx40SqG5vZOJ6XqYBbGf5X364KyHxtQRFGiyPscfc+EPstVGNVxhGO7Tjp 9MUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=BoTOo2Q0hAaQhRV9S4lq8HdMSQdYs79oTvCprCzExNE=; b=hEgJZkAb4a01IVnidDKOHlBGZOz1J7ckX/tu+aZna9XhwWWMXjMutDGP/sVEQ8JUO2 tpIg9MblJ77YUxpnwMSgqU1gKs2XZGb0ugEL0e+/+Rr+u6HVaFc4NY7Mw1PQ6JvfNmEw 9IXTsUBAVRs51GSWgae8q2lz90/ns7kXGLTrYHEegtsCSlPRxayWNIEjOi2fTygOSwh1 LwnaPOsTH39gqt0CuGQBMp0fnkWt+DcV4k/pJ0o2VOlqyq7kTPsD4D2nDQzknDUXfFk3 5cSC4YQathVl8AmvPZLX0zM2r1ydCIj9nUnCsY2COKNTDtGHyE1lScdKeSBcWNu6A6pU GlrA== X-Gm-Message-State: APjAAAV15H0nBXYOUukDdx0p8sIgBawRq56x6ar31e4Juq5OrPiywvCn tAnU2mgrwLUFI9l3k0IjBUU= X-Received: by 2002:a19:c1cc:: with SMTP id r195mr29910373lff.95.1563765166998; Sun, 21 Jul 2019 20:12:46 -0700 (PDT) Received: from localhost (h85-30-9-151.cust.a3fiber.se. [85.30.9.151]) by smtp.gmail.com with ESMTPSA id e13sm7350247ljg.102.2019.07.21.20.12.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 21 Jul 2019 20:12:45 -0700 (PDT) Date: Sun, 21 Jul 2019 20:07:04 -0700 From: Olof Johansson To: Leo Li Cc: "arm@kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "shawnguo@kernel.org" , "soc@kernel.org" Subject: Re: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3) Message-ID: <20190722030704.jg23kwxksh7ge4vn@localhost> References: <20190605194511.12127-1-leoyang.li@nxp.com> <20190617114948.7xxtpivve52c2jnb@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 08, 2019 at 06:48:17PM +0000, Leo Li wrote: > > > > -----Original Message----- > > From: Leo Li > > Sent: Monday, June 17, 2019 8:29 AM > > To: Olof Johansson > > Cc: arm@kernel.org; linux-arm-kernel@lists.infradead.org; linux- > > kernel@vger.kernel.org; shawnguo@kernel.org > > Subject: RE: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3) > > > > > > > > > -----Original Message----- > > > From: Olof Johansson > > > Sent: Monday, June 17, 2019 6:50 AM > > > To: Leo Li > > > Cc: arm@kernel.org; linux-arm-kernel@lists.infradead.org; linux- > > > kernel@vger.kernel.org; shawnguo@kernel.org > > > Subject: Re: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3) > > > > > > On Wed, Jun 05, 2019 at 02:45:11PM -0500, Li Yang wrote: > > > > Hi arm-soc maintainers, > > > > > > > > This is a rebase of patches that missed 5.2 merge window together > > > > with some new patches for QE. Please help to review and merge it. > > > > We would like this to be merged earlier because there are other > > > > patches depending on patches in this pull request. After this is > > > > merged in arm-soc, we can ask other sub-system maintainers to pull > > > > from this tag and apply additional patches. Thanks. > > > > > > Li, > > > > > > You never followed up with a reply, or removed, the previous tag. So > > > when we process the pull requests that come in, we've already merged it. > > > > Sorry about that. Will reply the previous pull request and remove the old tag > > if update is needed next time. > > > > > > > > So, I've merged the previous version. Can you send an incremental pull > > > request on top of that branch/tag instead of a rebase like this was, please? > > > > Actually the new pull request is based on the old pull request this time. I > > sent the new one as V2 hoping that you can see this first and avoid merging > > two times. Since you have already merged the first one, you can merge the > > second pull request as an incremental pull request directly. > > Hi Olof, > > I was on vacation for the past two weeks to follow up on this. Hope this is not too late for this merge window. Like I mentioned, the new tag is on top of the previous tag (you merged) so that it should be able to be merged incrementally. The only thing is that the description of the new tag also included patches you merged with old tag. Do you want me to regenerate the tag before you can merge it? Hi, I've now merged v2 into arm/drivers for the 5.4 merge window. If you need to add more material on top for 5.4, feel free to use it as the base that you send incremental pull requests on top of. Next time, it's probably easier if you re-generate a new pull request like I asked for -- I missed revisiting this since it seemed like a side follow up and not new material to merge. -Olof