All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jayachandran C <jnair@caviumnetworks.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org,
	Alex Williamson <alex.williamson@redhat.com>,
	iommu@lists.linux-foundation.org
Cc: Jayachandran C <jchandra@broadcom.com>,
	linux-arm-kernel@lists.infradead.org,
	Jon Masters <jcm@redhat.com>, Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v3 1/2] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT
Date: Wed, 22 Mar 2017 09:09:45 +0000	[thread overview]
Message-ID: <20170322090945.GA2907@localhost> (raw)
In-Reply-To: <1490172671-2648-2-git-send-email-jnair@caviumnetworks.com>

On Wed, Mar 22, 2017 at 08:51:10AM +0000, Jayachandran C wrote:

> From: Jayachandran C <jchandra@broadcom.com>

Looks like I did not fix up the author to my new mail ID. Please ignore
this part.

I can send out a clean revision if needed, until then please drop the
broadcom.com mail id in any reply to avoid bounces. Sorry for the mess up.

Thanks,
JC.

WARNING: multiple messages have this Message-ID (diff)
From: Jayachandran C <jnair@caviumnetworks.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org,
	Alex Williamson <alex.williamson@redhat.com>,
	iommu@lists.linux-foundation.org
Cc: Jon Masters <jcm@redhat.com>,
	Jayachandran C <jchandra@broadcom.com>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT
Date: Wed, 22 Mar 2017 09:09:45 +0000	[thread overview]
Message-ID: <20170322090945.GA2907@localhost> (raw)
In-Reply-To: <1490172671-2648-2-git-send-email-jnair@caviumnetworks.com>

On Wed, Mar 22, 2017 at 08:51:10AM +0000, Jayachandran C wrote:

> From: Jayachandran C <jchandra@broadcom.com>

Looks like I did not fix up the author to my new mail ID. Please ignore
this part.

I can send out a clean revision if needed, until then please drop the
broadcom.com mail id in any reply to avoid bounces. Sorry for the mess up.

Thanks,
JC.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: jnair@caviumnetworks.com (Jayachandran C)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT
Date: Wed, 22 Mar 2017 09:09:45 +0000	[thread overview]
Message-ID: <20170322090945.GA2907@localhost> (raw)
In-Reply-To: <1490172671-2648-2-git-send-email-jnair@caviumnetworks.com>

On Wed, Mar 22, 2017 at 08:51:10AM +0000, Jayachandran C wrote:

> From: Jayachandran C <jchandra@broadcom.com>

Looks like I did not fix up the author to my new mail ID. Please ignore
this part.

I can send out a clean revision if needed, until then please drop the
broadcom.com mail id in any reply to avoid bounces. Sorry for the mess up.

Thanks,
JC.

  reply	other threads:[~2017-03-22  9:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22  8:51 [PATCH v3 0/2] Handle Cavium ThunderX2 PCI topology quirk Jayachandran C
2017-03-22  8:51 ` Jayachandran C
2017-03-22  8:51 ` Jayachandran C
2017-03-22  8:51 ` [PATCH v3 1/2] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT Jayachandran C
2017-03-22  8:51   ` Jayachandran C
2017-03-22  8:51   ` Jayachandran C
2017-03-22  9:09   ` Jayachandran C [this message]
2017-03-22  9:09     ` Jayachandran C
2017-03-22  9:09     ` Jayachandran C
2017-03-22  8:51 ` [PATCH v3 2/2] PCI: quirks: Fix ThunderX2 dma alias handling Jayachandran C
2017-03-22  8:51   ` Jayachandran C
     [not found] ` <1490172671-2648-1-git-send-email-jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2017-03-22 15:13   ` [PATCH v3 0/2] Handle Cavium ThunderX2 PCI topology quirk Jon Masters
2017-03-22 15:13     ` Jon Masters
2017-03-22 15:13     ` Jon Masters
2017-03-24 12:44     ` Jayachandran C
2017-03-24 12:44       ` Jayachandran C
2017-03-24 12:44       ` Jayachandran C

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=20170322090945.GA2907@localhost \
    --to=jnair@caviumnetworks.com \
    --cc=alex.williamson@redhat.com \
    --cc=helgaas@kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jchandra@broadcom.com \
    --cc=jcm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    /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.