mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
	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, 4 Oct 2017 11:38:01 -0700	[thread overview]
Message-ID: <976729bf-5985-e989-183b-70cd28a3a983@synopsys.com> (raw)
In-Reply-To: <1507111778.11691.9.camel@pengutronix.de>

Hi Philipp,

On 10/04/2017 03:09 AM, Philipp Zabel wrote:
>> 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.

Thanks for creating this !

Here's the plan. I have some changes queued up for 4.14-rc4 (which includes a 
adding a reset workaround since the driver is not in for 4.14).
Once that is merged in mainline this week, I will create my for-next based on 
4.14-rc4 + git pull --no-ff ur-branch + reverts for reset hack above.

OK ?

-Vineet

  reply	other threads:[~2017-10-04 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 14:28 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
2017-10-04 18:38         ` Vineet Gupta [this message]
2017-10-09 18:25         ` Vineet Gupta
2017-10-27 20:57           ` 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=976729bf-5985-e989-183b-70cd28a3a983@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Eugeniy.Paltsev@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=p.zabel@pengutronix.de \
    --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

all inboxes | Powered by JetHome®