linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-sh@vger.kernel.org, linux-pci@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 0/8] SH7786 PCIe support fixes
Date: Mon, 08 Jan 2018 22:27:11 +0000	[thread overview]
Message-ID: <20180108232711.461a492d@windsurf> (raw)
In-Reply-To: <20180108221258.GA31640@bhelgaas-glaptop.roam.corp.google.com>

Hello,

On Mon, 8 Jan 2018 16:12:58 -0600, Bjorn Helgaas wrote:

> > > Thomas Petazzoni (8):
> > >   arch/sh: add sh7786_mm_sel() function
> > >   arch/sh: make the DMA mapping operations observe dev->dma_pfn_offset
> > >   arch/sh: pci: don't use disabled resources
> > >   arch/sh: pcie-sh7786: mark unavailable PCI resource as disabled
> > >   arch/sh: pcie-sh7786: exclude unusable PCI MEM areas
> > >   arch/sh: pcie-sh7786: adjust PCI MEM and IO regions
> > >   arch/sh: pcie-sh7786: adjust the memory mapping
> > >   arch/sh: pcie-sh7786: handle non-zero DMA offset  
> > 
> > It's been a month. Any feedback on those patches ?  
> 
> I'm assuming Yoshinori and Rich will handle these.  Let me know if
> otherwise.

Yes, it's all in arch/sh, so I assume the SH maintainers will take care
of those patches. I mainly CC'ed the PCI maintainers + mailing list for
information, and to get additional feedback on PCI specific topics if
there's any.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-08 22:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:08 [PATCH 0/8] SH7786 PCIe support fixes Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 1/8] arch/sh: add sh7786_mm_sel() function Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 2/8] arch/sh: make the DMA mapping operations observe dev->dma_pfn_offset Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 3/8] arch/sh: pci: don't use disabled resources Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 4/8] arch/sh: pcie-sh7786: mark unavailable PCI resource as disabled Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 5/8] arch/sh: pcie-sh7786: exclude unusable PCI MEM areas Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 6/8] arch/sh: pcie-sh7786: adjust PCI MEM and IO regions Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 7/8] arch/sh: pcie-sh7786: adjust the memory mapping Thomas Petazzoni
2017-12-04 15:09 ` [PATCH 8/8] arch/sh: pcie-sh7786: handle non-zero DMA offset Thomas Petazzoni
2018-01-07 15:06 ` [PATCH 0/8] SH7786 PCIe support fixes Thomas Petazzoni
2018-01-08 22:12   ` Bjorn Helgaas
2018-01-08 22:27     ` Thomas Petazzoni [this message]
2018-02-26 13:32   ` Thomas Petazzoni
2018-02-19 16:22 ` Thomas Petazzoni

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=20180108232711.461a492d@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=bhelgaas@google.com \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=ysato@users.sourceforge.jp \
    /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).