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;
From:   Leo Li <leoyang.li@nxp.com>
To:     Olof Johansson <olof@lixom.net>
CC:     "arm@kernel.org" <arm@kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "shawnguo@kernel.org" <shawnguo@kernel.org>,
        "soc@kernel.org" <soc@kernel.org>
Subject: RE: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3)
Thread-Topic: [GIT PULL v2] updates to soc/fsl drivers for next(v5.3)
Thread-Index: AQHVJQRRM+rvlXmln0KUqEroTyzJyqaf1DJAgCFaZTA=
Date:   Mon, 8 Jul 2019 18:48:17 +0000
Message-ID: <VE1PR04MB668750E96558796A2E81DB678FF60@VE1PR04MB6687.eurprd04.prod.outlook.com>
References: <20190605194511.12127-1-leoyang.li@nxp.com>
 <20190617114948.7xxtpivve52c2jnb@localhost>
 <VE1PR04MB668773AB42154134CE18A6AB8FEB0@VE1PR04MB6687.eurprd04.prod.outlook.com>
In-Reply-To: <VE1PR04MB668773AB42154134CE18A6AB8FEB0@VE1PR04MB6687.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b85f1e69-d2d2-450d-09b7-08d703d4d775
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 18:48:17.7477
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: leoyang.li@nxp.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1PR04MB6672
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> -----Original Message-----
> From: Leo Li
> Sent: Monday, June 17, 2019 8:29 AM
> To: Olof Johansson <olof@lixom.net>
> 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)
>=20
>=20
>=20
> > -----Original Message-----
> > From: Olof Johansson <olof@lixom.net>
> > Sent: Monday, June 17, 2019 6:50 AM
> > To: Leo Li <leoyang.li@nxp.com>
> > 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=
.
>=20
> Sorry about that.  Will reply the previous pull request and remove the ol=
d tag
> if update is needed next time.
>=20
> >
> > 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, pl=
ease?
>=20
> 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 mergi=
ng
> two times.  Since you have already merged the first one, you can merge th=
e
> 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 i=
s 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 th=
e tag before you can merge it?

Regards,
Leo