From: Philipp Zabel <p.zabel@pengutronix.de>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2] ARC: reset: introduce AXS10x reset driver
Date: Wed, 04 Oct 2017 12:09:38 +0200 [thread overview]
Message-ID: <1507111778.11691.9.camel@pengutronix.de> (raw)
In-Reply-To: <1505753484.9807.18.camel@pengutronix.de>
Hi Vineet,
On Mon, 2017-09-18 at 18:51 +0200, Philipp Zabel wrote:
> > Will it be OK for you to apply the corresponding DT update for
> > platform - that way
> > I don't have to keep track of when ur branch hits mainline etc.
> >
> > The chances of any ensuing conflicts are pretty rare - and easy to resolve if at all.
> >
> > If so, Eugeniy can send the patch ur way !
>
> Maybe it is better to do this the other way around? I can put this patch
> on a stable reset/arc branch for you to merge before applying the reset
> DT updates.
Have you come to a decision on this?
Just in case, I have removed the AXS10x driver from the reset/next
branch and put it on its own branch:
git://git.pengutronix.de/git/pza/linux.git reset/arc
This branch is immutable and I'll merge it into reset/next before
submitting the branch for v4.15-rc1.
regards
Philipp
next prev parent reply other threads:[~2017-10-04 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:28 [PATCH v2] ARC: reset: introduce AXS10x reset driver Eugeniy Paltsev
2017-09-18 12:07 ` Philipp Zabel
2017-09-18 16:14 ` Vineet Gupta
2017-09-18 16:51 ` Philipp Zabel
2017-10-04 10:09 ` Philipp Zabel [this message]
[not found] ` <1507111778.11691.9.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-10-04 18:38 ` Vineet Gupta
2017-10-09 18:25 ` Vineet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507111778.11691.9.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).