From: David Miller <davem@davemloft.net>
To: chris.leech@gmail.com, christopher.leech@intel.com
Cc: dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
neilb@suse.de, galak@kernel.crashing.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] I/OAT: remove CPU hotplug lock from net_dma_rebalance
Date: Wed, 02 Aug 2006 14:20:34 -0700 (PDT) [thread overview]
Message-ID: <20060802.142034.94556682.davem@davemloft.net> (raw)
In-Reply-To: <41b516cb0608011133r2332161dx4b43a845bfa74062@mail.gmail.com>
From: "Chris Leech" <christopher.leech@intel.com>
Date: Tue, 1 Aug 2006 11:33:02 -0700
> if (net_dma_count == 0) {
> for_each_online_cpu(cpu)
>
> rcu_assign_pointer(per_cpu(softnet_data.net_dma, cpu), NULL);
> - unlock_cpu_hotplug();
Why is proper patch submission so damn difficult for people?
This patch is corrupted severely.
I'm fixing this up since it's such an obvious patch, but this
issue is getting really rediculious. I can't believe how many
people submit line-wrapped, tab destroyed, patches these days.
prev parent reply other threads:[~2006-08-02 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 18:33 Chris Leech
2006-08-02 21:20 ` 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=20060802.142034.94556682.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris.leech@gmail.com \
--cc=christopher.leech@intel.com \
--cc=dan.j.williams@intel.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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
all inboxes | Powered by JetHome®