From: Julien Grall <julien.grall@linaro.org>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"manish.jaggi@caviumnetworks.com"
<manish.jaggi@caviumnetworks.com>, "tim@xen.org" <tim@xen.org>,
"stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH for 4.6 07/13] xen: Introduce a generic way to describe device
Date: Thu, 18 Dec 2014 08:52:28 +0000 [thread overview]
Message-ID: <549295CC.2060309@linaro.org> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AC04044@SHSMSX104.ccr.corp.intel.com>
Hello Zhang,
Please respect the netiquette and avoid lines over 80 characters.
On 18/12/2014 01:12, Zhang, Yang Z wrote:
> I'd suggest splitting the changes to common code to a separate patch and also CC the VT-d/AMD maintainers.
This patch is already common code. Though, there was some changes in
arch/arm because of interdependency. Splitting more won't make more sense.
> Because I didn't find those definitions when reviewing the 8th patch
and I need to search the whole patch set to find them.
it's not a new problem. A patch may have a dependency on another patch
who has dependency on another one... This would end up to be CCed on
every patch and spam your inbox.
I usually provide a git repo with my patch series in the cover letter.
So if you miss anything you can look to the code and found the relevant
patch.
Anyway... I will CC next time
Sincerely yours,
--
Julien Grall
next prev parent reply other threads:[~2014-12-18 8:52 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 20:08 [PATCH for 4.6 00/13] xen/arm: Resync the SMMU driver with the Linux one Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 01/13] xen/arm: gic-v2: Change the device name in DT_DEVICE_START Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 02/13] xen/arm: vgic: Drop unecessary include asm/device.h Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 03/13] xen: Introduce ACCESS_ONCE macro Julien Grall
2014-12-17 10:05 ` Jan Beulich
2014-12-17 12:54 ` Julien Grall
2014-12-17 17:10 ` Jan Beulich
2014-12-17 17:52 ` Andrew Cooper
2014-12-18 15:58 ` Julien Grall
2014-12-18 15:58 ` Julien Grall
2015-01-15 13:39 ` Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 04/13] xen/dt: Extend dt_device_match to possibly store data Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 05/13] xen/arm: device: Rename device_type into device_match Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 06/13] xen/iommu: arm: Remove temporary the SMMU driver Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 07/13] xen: Introduce a generic way to describe device Julien Grall
2014-12-17 10:16 ` Jan Beulich
2014-12-17 10:30 ` Julien Grall
2014-12-17 10:46 ` Jan Beulich
2014-12-17 13:03 ` Julien Grall
2014-12-17 17:17 ` Jan Beulich
2014-12-18 15:56 ` Julien Grall
2014-12-18 16:02 ` Jan Beulich
2014-12-18 16:07 ` Julien Grall
2014-12-18 1:12 ` Zhang, Yang Z
2014-12-18 8:52 ` Julien Grall [this message]
2014-12-16 20:08 ` [PATCH for 4.6 08/13] xen/iommu: Consolidate device assignment ops into a single set Julien Grall
2014-12-17 10:20 ` Jan Beulich
2014-12-16 20:08 ` [PATCH for 4.6 09/13] xen/arm: Describe device supported by a driver with dt_match_node Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 10/13] xen/iommu: arm: Import the SMMU driver from Linux Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 11/13] xen/iommu: smmu: Check for duplicate stream IDs when registering master devices Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 12/13] xen/iommu: smmu: Introduce automatic stream-id-masking Julien Grall
2014-12-16 20:08 ` [PATCH for 4.6 13/13] xen/iommu: smmu: Add Xen specific code to be able to use the driver Julien Grall
2015-02-18 1:02 ` Manish
2015-02-18 11:47 ` Julien Grall
2015-02-18 11:54 ` Julien Grall
2015-02-18 17:30 ` Jaggi, Manish
2015-02-18 18:22 ` Julien Grall
2015-02-19 2:55 ` Manish
2015-02-19 6:01 ` Julien Grall
2015-02-19 7:16 ` Manish
2015-02-19 10:34 ` Andrew Cooper
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=549295CC.2060309@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.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.