From: David Miller <davem@davemloft.net>
To: ross.lagerwall@citrix.com
Cc: xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
jgross@suse.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] xen-netfront: Fix race between device setup and open
Date: Thu, 11 Jan 2018 11:36:44 -0500 (EST) [thread overview]
Message-ID: <20180111.113644.936229336500292786.davem@davemloft.net> (raw)
In-Reply-To: <0650f0ec-51ce-70ee-cd8a-6620f0c9eea8@citrix.com>
From: Ross Lagerwall <ross.lagerwall@citrix.com>
Date: Thu, 11 Jan 2018 16:27:20 +0000
> On 01/11/2018 04:08 PM, David Miller wrote:
>> From: Ross Lagerwall <ross.lagerwall@citrix.com>
>> Date: Thu, 11 Jan 2018 15:49:07 +0000
>>
>>> I've now added CC'd netdev on the other two.
>> That doesn't work.
>> If you don't post the originals explicitly to netdev then it won't
>> get properly queued in patchwork.
>>
>
> The series fixes two crashes when using netfront. The first is
> actually fixed in Xen common code, not netfront, which is why I only
> CC'd netdev on the second. I can resend the originals to netdev if you
> want but IMO it is not necessary.
Everyone who reviews the networking side will appreciate the full
context of the patch series so they can review the networking part
in proper context.
And if it is decided that these changes should go via my GIT tree
wouldn't you want it to be all setup properly for that already without
having to do anything more on your part?
I don't see what the resistence is to giving people more information
and allowing more flexibility for integrating and reviewing your
work.
next prev parent reply other threads:[~2018-01-11 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 9:36 [PATCH 0/2] Fix a couple of crashes in netfront Ross Lagerwall
2018-01-11 9:36 ` [PATCH 1/2] xen/grant-table: Use put_page instead of free_page Ross Lagerwall
2018-01-11 15:48 ` Ross Lagerwall
2018-01-16 18:47 ` Boris Ostrovsky
2018-01-11 9:36 ` [PATCH 2/2] xen-netfront: Fix race between device setup and open Ross Lagerwall
2018-01-11 15:26 ` David Miller
2018-01-11 15:49 ` Ross Lagerwall
2018-01-11 16:08 ` David Miller
2018-01-11 16:27 ` Ross Lagerwall
2018-01-11 16:36 ` David Miller [this message]
2018-01-16 18:56 ` Boris Ostrovsky
2018-01-11 15:48 ` [PATCH 0/2] Fix a couple of crashes in netfront Ross Lagerwall
2018-02-06 14:52 ` Juergen Gross
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=20180111.113644.936229336500292786.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xenproject.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