From: Veaceslav Falico <vfalico@redhat.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
dingtianhong@huawei.com, fubar@us.ibm.com, andy@greyhouse.net,
nikolay@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/10] bonding: rebuild the lock use for bond monitor
Date: Wed, 13 Nov 2013 10:26:06 +0100 [thread overview]
Message-ID: <20131113092606.GG19702@redhat.com> (raw)
In-Reply-To: <1384298787.3802.59.camel@bwh-desktop.uk.level5networks.com>
On Tue, Nov 12, 2013 at 11:26:27PM +0000, Ben Hutchings wrote:
>On Fri, 2013-11-08 at 01:45 -0500, David Miller wrote:
>> Such patches should not be submitted at this time, the merge window
>> has openned up and therefore the net-next tree is closed.
>>
>> Please wait for the merge window to close and the net-next tree
>> to open back up before submitting these changes.
>
>These look like bug fixes that should have been submitted for the net
>tree.
I am not really sure that it's suitable for net tree, cause these aren't
really bugfixes - but rather locking removal. It might fix/improve some
situations - but the changes touch really sensitive parts and I think they
should go through net-next, to brew a little.
>
>Ben.
>
>--
>Ben Hutchings, Staff Engineer, Solarflare
>Not speaking for my employer; that's the marketing department's job.
>They asked us to note that Solarflare product names are trademarked.
>
next prev parent reply other threads:[~2013-11-13 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 2:07 [PATCH net-next v2 0/10] bonding: rebuild the lock use for bond monitor Ding Tianhong
2013-11-08 6:45 ` David Miller
2013-11-12 23:26 ` Ben Hutchings
2013-11-13 9:26 ` Veaceslav Falico [this message]
2013-11-08 16:32 ` Nikolay Aleksandrov
2013-11-09 8:03 ` Ding Tianhong
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=20131113092606.GG19702@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.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.