public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: green@linuxhacker.ru
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH 0/2] Lustre: get rid of deprecated cpumask calls
Date: Mon,  2 Mar 2015 01:01:45 -0500	[thread overview]
Message-ID: <1425276107-15543-1-git-send-email-green@linuxhacker.ru> (raw)

From: Oleg Drokin <green@linuxhacker.ru>

A recent crash report with CONFIG_CPUMASK_OFFSTACK enabled
set off a chain of emails through which I learned that cpus_* functions
are deprecated and should not be really used to operate on cpumasks.

These two patches do just that, replacing cpus_* and cpu_* calls
with cpumask_ equivalents, getting rid of a sizable number or
NR_CPUS references

please consider.

Oleg Drokin (2):
  staging/lustre/ptlrpc: Do not use deprecated cpus_* functions
  staging/lustre/libcfs: replace deprecated cpus_ calls with cpumask_

 .../staging/lustre/lustre/libcfs/linux/linux-cpu.c | 78 +++++++++++-----------
 drivers/staging/lustre/lustre/ptlrpc/ptlrpcd.c     |  8 +--
 drivers/staging/lustre/lustre/ptlrpc/service.c     |  9 +--
 3 files changed, 46 insertions(+), 49 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-03-02  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  6:01 green [this message]
2015-03-02  6:01 ` [PATCH 1/2] staging/lustre/ptlrpc: Do not use deprecated cpus_* functions green
2015-03-02  6:01 ` [PATCH 2/2] staging/lustre/libcfs: replace deprecated cpus_ calls with cpumask_ green

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=1425276107-15543-1-git-send-email-green@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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