linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe
Date: Tue, 21 Jul 2015 14:04:33 -0700	[thread overview]
Message-ID: <55AEB3E1.6010405@broadcom.com> (raw)
In-Reply-To: <55AEB094.1090601@broadcom.com>



On 7/21/2015 1:50 PM, Ray Jui wrote:
> 
> 
> On 7/21/2015 1:30 PM, Bjorn Helgaas wrote:
>> On Wed, Jul 15, 2015 at 09:39:20PM -0700, Ray Jui wrote:

>> I see that your v1 patch added #ifdef CONFIG_ARM around sysdata at its
>> original location below, and you mentioned that you took Arnd's advice to
>> move sysdata to the beginning of the structure, but I don't see Arnd's
>> email on the list.
>>
> 
> Sorry maybe you need to elaborate here. Am I supposed to add Arnd's name
> in the commit message? Other than that, Arnd is on this email thread.
> 

For your previous question: when Arnd replied, he only replied to me but
did not reply to all, that's why you cannot find his email....

Ray

  reply	other threads:[~2015-07-21 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  4:39 [PATCH v3 0/4] Add Broadcom North Star 2 support Ray Jui
2015-07-16  4:39 ` [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe Ray Jui
2015-07-21 20:30   ` Bjorn Helgaas
2015-07-21 20:50     ` Ray Jui
2015-07-21 21:04       ` Ray Jui [this message]
2015-07-21 22:02       ` Bjorn Helgaas
2015-07-22  0:01         ` Ray Jui
2015-07-16  4:39 ` [PATCH v3 2/4] PCI: iproc: Fix ARM64 dependency in Kconfig Ray Jui
2015-07-16  4:39 ` [PATCH v3 3/4] arm64: Add Broadcom iProc family support Ray Jui
2015-07-16  4:39 ` [PATCH v3 4/4] arm64: dts: Add Broadcom North Star 2 support Ray Jui

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=55AEB3E1.6010405@broadcom.com \
    --to=rjui@broadcom.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).