From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
Cc: raghuram.kothakota@oracle.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] sunvnet: Fixes to avoid soft lockup in sunvnet
Date: Mon, 11 Aug 2014 14:08:57 -0700 (PDT) [thread overview]
Message-ID: <20140811.140857.65481151389542468.davem@davemloft.net> (raw)
In-Reply-To: <20140811210354.GB20351@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Mon, 11 Aug 2014 17:03:54 -0400
> On (08/11/14 13:56), David Miller wrote:
>>
>> Please don't fix multiple things in one huge patch, split up the
>> changes into separate easily reviewed patches.
>
> So there were 4 different sources of soft-lockup here, each of them
> was just a few lines of change. Do you really want these as 4 patches?
Absolutely, the different lockup changes have different implications
and different sets of issues to consider.
prev parent reply other threads:[~2014-08-11 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 19:48 [PATCH net-next] sunvnet: Fixes to avoid soft lockup in sunvnet Sowmini Varadhan
2014-08-11 20:56 ` David Miller
2014-08-11 21:03 ` Sowmini Varadhan
2014-08-11 21:08 ` David Miller [this message]
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=20140811.140857.65481151389542468.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=raghuram.kothakota@oracle.com \
--cc=sowmini.varadhan@oracle.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 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).