From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/2] Add support for ARM CCN-502 interconnect
Date: Mon, 19 Jun 2017 17:06:11 +0100 [thread overview]
Message-ID: <1497888371.28673.12.camel@arm.com> (raw)
In-Reply-To: <d9491ea8-ae9a-b620-c5fd-44cd6c78d49c@broadcom.com>
On Fri, 2017-06-16 at 13:39 -0700, Scott Branden wrote:
> Arnd,
>
> Should this patchset go through the ARM maintainers?
Unless something changed in the last months, these patches should go
through arm-soc. Arnd is probably just waiting for me to send a pull
request. And indeed shame on me that I still haven't got around doing
this. Promise to do so tomorrow.
Regards and apologies
Pawel
prev parent reply other threads:[~2017-06-19 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 6:39 [PATCH RESEND 0/2] Add support for ARM CCN-502 interconnect Scott Branden
2017-06-16 6:39 ` [PATCH RESEND 1/2] dt-bindings: arm-ccn: Add bindings info for CCN-502 compatible string Scott Branden
2017-06-16 6:39 ` [PATCH RESEND 2/2] bus: arm-ccn: Enable stats for CCN-502 interconnect Scott Branden
2017-06-16 20:39 ` [PATCH RESEND 0/2] Add support for ARM " Scott Branden
2017-06-19 16:06 ` Pawel Moll [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=1497888371.28673.12.camel@arm.com \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).