From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v11 0/3]add PCIe driver for Kirin PCIe
Date: Mon, 3 Jul 2017 11:47:27 +0100 [thread overview]
Message-ID: <20170703104727.GB1573@arm.com> (raw)
In-Reply-To: <20170702233657.GA13507@bhelgaas-glaptop.roam.corp.google.com>
On Sun, Jul 02, 2017 at 06:36:57PM -0500, Bjorn Helgaas wrote:
> [+cc Catalin, Will, linux-arm-kernel]
>
> Applied patches 2 & 3 to pci/host-kirin for v4.13.
>
> I would like a MAINTAINERS update, too. If you send me that, I'll
> squash it into the driver patch.
>
> Catalin, Will, how do you want to handle the
> arch/arm64/configs/defconfig change (patch 3)? It's currently on my
> branch, but I'm happy to drop it if another route is better.
defconfig updates usually go through arm-soc, via the relevant platform
maintainer, so it would be best to follow that route here too otherwise
you'll probably see conflicts in -next.
Will
next prev parent reply other threads:[~2017-07-03 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170619102349.50652-1-songxiaowei@hisilicon.com>
2017-07-02 23:36 ` [PATCH v11 0/3]add PCIe driver for Kirin PCIe Bjorn Helgaas
2017-07-03 10:47 ` Will Deacon [this message]
2017-07-03 12:55 ` Bjorn Helgaas
2017-07-03 13:04 ` Guodong Xu
2017-07-03 13:32 ` Wei Xu
2017-07-04 2:03 ` Guodong Xu
2017-08-15 13:28 ` Wei Xu
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=20170703104727.GB1573@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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