All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Jonathan Chocron <jonnyc@amazon.com>,
	Rob Herring <robh@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH dwc-next v2 0/2] PCI: dwc: remove useless dw_pcie_ops
Date: Mon, 25 Jan 2021 16:25:42 +0000	[thread overview]
Message-ID: <20210125162542.GA5795@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20201120191611.7b84a86b@xhacker.debian>

On Fri, Nov 20, 2020 at 07:16:11PM +0800, Jisheng Zhang wrote:
> Some designware based device driver especially host only driver may
> work well with the default read_dbi/write_dbi/link_up implementation
> in pcie-designware.c, thus remove the assumption to simplify those
> drivers.
> 
> Since v1:
>   - rebase to the latest dwc-next
> 
> Jisheng Zhang (2):
>   PCI: dwc: Don't assume the ops in dw_pcie always exists
>   PCI: dwc: al: Remove useless dw_pcie_ops
> 
>  drivers/pci/controller/dwc/pcie-al.c              |  4 ----
>  drivers/pci/controller/dwc/pcie-designware-ep.c   |  8 +++-----
>  drivers/pci/controller/dwc/pcie-designware-host.c |  2 +-
>  drivers/pci/controller/dwc/pcie-designware.c      | 14 +++++++-------
>  4 files changed, 11 insertions(+), 17 deletions(-)

Would you mind rebasing it against my current pci/dwc branch please ?

I shall apply it then.

Thanks,
Lorenzo

      parent reply	other threads:[~2021-01-25 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 11:16 [PATCH dwc-next v2 0/2] PCI: dwc: remove useless dw_pcie_ops Jisheng Zhang
2020-11-20 11:17 ` [PATCH dwc-next v2 2/2] PCI: dwc: al: Remove " Jisheng Zhang
2021-01-25 20:57   ` Chocron, Jonathan
2020-11-20 11:17 ` [PATCH dwc-next v2 1/2] PCI: dwc: Don't assume the ops in dw_pcie always exists Jisheng Zhang
2021-01-25 16:25 ` Lorenzo Pieralisi [this message]

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=20210125162542.GA5795@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=Jisheng.Zhang@synaptics.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=jonnyc@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@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 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.