All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	richardcochran@gmail.com, Russell King <linux@arm.linux.org.uk>,
	Suman Anna <s-anna@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, nsekhar@ti.com
Subject: Re: [PATCH v2 3/3] pci: dra7xx: use pdata callbacks to perform reset
Date: Wed, 13 Jan 2016 09:19:14 -0800	[thread overview]
Message-ID: <20160113171913.GH12777@atomide.com> (raw)
In-Reply-To: <1452667666-17533-4-git-send-email-kishon@ti.com>

* Kishon Vijay Abraham I <kishon@ti.com> [160112 22:48]:
> Use platform populated reset assert and deassert
> callbacks to perform reset of PCIe.
> 
> Use these callbacks until a reset interface using drivers/reset
> is available for the purpose.

This one has a dependency to the second patch for the platform
data.

Bjorn, how do you prefer to merge this once there are no more
comments?

How about I set up an immutable branch against v4.5-rc1 with
just these three patches that we can both then merge in?

My preference is to add this to linux next after the merge
window for v4.6. Bjorn, if you want it merged as fixes, I'm
fine with that too naturally.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] pci: dra7xx: use pdata callbacks to perform reset
Date: Wed, 13 Jan 2016 09:19:14 -0800	[thread overview]
Message-ID: <20160113171913.GH12777@atomide.com> (raw)
In-Reply-To: <1452667666-17533-4-git-send-email-kishon@ti.com>

* Kishon Vijay Abraham I <kishon@ti.com> [160112 22:48]:
> Use platform populated reset assert and deassert
> callbacks to perform reset of PCIe.
> 
> Use these callbacks until a reset interface using drivers/reset
> is available for the purpose.

This one has a dependency to the second patch for the platform
data.

Bjorn, how do you prefer to merge this once there are no more
comments?

How about I set up an immutable branch against v4.5-rc1 with
just these three patches that we can both then merge in?

My preference is to add this to linux next after the merge
window for v4.6. Bjorn, if you want it merged as fixes, I'm
fine with that too naturally.

Regards,

Tony

  reply	other threads:[~2016-01-13 17:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  6:47 [PATCH v2 0/3] dra7xx: get pcie working in mainline Kishon Vijay Abraham I
2016-01-13  6:47 ` Kishon Vijay Abraham I
2016-01-13  6:47 ` Kishon Vijay Abraham I
2016-01-13  6:47 ` [PATCH v2 1/3] ARM: DRA7: hwmod: Add reset data for PCIe Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13 17:13   ` Tony Lindgren
2016-01-13 17:13     ` Tony Lindgren
2016-01-13 17:46     ` Suman Anna
2016-01-13 17:46       ` Suman Anna
2016-01-13 17:46       ` Suman Anna
2016-01-13  6:47 ` [PATCH v2 2/3] ARM: DRA7: add pdata-quirks to do reset of PCIe Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13 17:35   ` Suman Anna
2016-01-13 17:35     ` Suman Anna
2016-01-13 17:35     ` Suman Anna
2016-01-13  6:47 ` [PATCH v2 3/3] pci: dra7xx: use pdata callbacks to perform reset Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13  6:47   ` Kishon Vijay Abraham I
2016-01-13 17:19   ` Tony Lindgren [this message]
2016-01-13 17:19     ` Tony Lindgren
2016-01-13 17:51   ` Suman Anna
2016-01-13 17:51     ` Suman Anna
2016-01-13 17:51     ` Suman Anna
2016-01-14  8:37     ` Kishon Vijay Abraham I
2016-01-14  8:37       ` Kishon Vijay Abraham I
2016-01-14  8:37       ` Kishon Vijay Abraham I
2016-01-14 13:28       ` Kishon Vijay Abraham I
2016-01-14 13:28         ` Kishon Vijay Abraham I
2016-01-14 13:28         ` Kishon Vijay Abraham I

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=20160113171913.GH12777@atomide.com \
    --to=tony@atomide.com \
    --cc=bhelgaas@google.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nsekhar@ti.com \
    --cc=richardcochran@gmail.com \
    --cc=s-anna@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.