[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160629215704.GA29796@pengutronix.de>
Date: Wed, 29 Jun 2016 23:57:04 +0200
From: Philipp Zabel <pza@...gutronix.de>
To: Lee Jones <lee.jones@...aro.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...inux.com, maxime.coquelin@...com,
srinivas.kandagatla@...il.com, kishon@...com, balbi@...nel.org,
gregkh@...uxfoundation.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH 4/7] reset: Supply *_shared variant calls when using
*_optional APIs
Hi Lee,
On Wed, Jun 29, 2016 at 10:37:34AM +0100, Lee Jones wrote:
[...]
> > > > If that is not the case, go ahead. Otherwise I could provide
> > > > a tag at commit 2485394d9e0b ("reset: TRIVIAL: Add line break at same
> > > > place for similar APIs") for you to merge.
> > >
> > > Yes please. If you could tag a branch containing commit:
> > >
> > > reset: Supply *_shared variant calls when using *_optional APIs
> > >
> > > ... that would be perfect. Would you mind sending me the tag name
> > > ASAP please, since I am ready to send my pull-request to Linus.
> >
> > git://git.pengutronix.de/git/pza/linux.git tags/reset-shared-optional
>
> Ah! If I rebase on that tag, I will also take in all of the patches
> between it and v4.7-rc1, which is 14 commits. Is there any way you
> can place it onto it's own branch, then we both merge it into our
> respective trees?
I have now moved your patches into their own branch at
git://git.pengutronix.de/git/pza/linux.git tags/reset-explicit-api
and merged that back in.
regards
Philipp
Powered by blists - more mailing lists