All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org, mingo@elte.hu, rusty@rustcorp.com.au
Subject: Re: cpumask change causes sparc build bustage
Date: Sun, 11 Jan 2009 22:29:07 +0000	[thread overview]
Message-ID: <496A72B3.8010105@sgi.com> (raw)
In-Reply-To: <20090111.135029.199678338.davem@davemloft.net>

David Miller wrote:
> From: Mike Travis <travis@sgi.com>
> Date: Sun, 11 Jan 2009 08:49:46 -0800
> 
>> Thanks for fixing it.  In actuality though, it should return cpu_mask_all
>> instead of CPU_MASK_ALL_PTR but that's a small nit.
> 
> CPU_MASK_ALL_PTR is defined to &cpu_mask_all, that's why I used it, to
> be consistent with the other macro using CPU_MASK_ALL right above it.

It's not a big deal.  CPU_MASK_ALL_PTR is one of those "bandaids" to
keep current code working until it's all been cleansed of the old
cpumask_t functions.  Rusty's so-called "big hammer" patch.

Thanks,
Mike


WARNING: multiple messages have this Message-ID (diff)
From: Mike Travis <travis@sgi.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org, mingo@elte.hu, rusty@rustcorp.com.au
Subject: Re: cpumask change causes sparc build bustage
Date: Sun, 11 Jan 2009 14:29:07 -0800	[thread overview]
Message-ID: <496A72B3.8010105@sgi.com> (raw)
In-Reply-To: <20090111.135029.199678338.davem@davemloft.net>

David Miller wrote:
> From: Mike Travis <travis@sgi.com>
> Date: Sun, 11 Jan 2009 08:49:46 -0800
> 
>> Thanks for fixing it.  In actuality though, it should return cpu_mask_all
>> instead of CPU_MASK_ALL_PTR but that's a small nit.
> 
> CPU_MASK_ALL_PTR is defined to &cpu_mask_all, that's why I used it, to
> be consistent with the other macro using CPU_MASK_ALL right above it.

It's not a big deal.  CPU_MASK_ALL_PTR is one of those "bandaids" to
keep current code working until it's all been cleansed of the old
cpumask_t functions.  Rusty's so-called "big hammer" patch.

Thanks,
Mike


  reply	other threads:[~2009-01-11 22:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  8:31 cpumask change causes sparc build bustage David Miller
2009-01-11  8:31 ` David Miller
2009-01-11  9:50 ` Stephen Rothwell
2009-01-11  9:50   ` Stephen Rothwell
2009-01-11 12:06   ` David Miller
2009-01-11 12:06     ` David Miller
2009-01-11 12:13     ` Ingo Molnar
2009-01-11 12:13       ` Ingo Molnar
2009-01-11 16:49     ` Mike Travis
2009-01-11 16:49       ` Mike Travis
2009-01-11 21:50       ` David Miller
2009-01-11 21:50         ` David Miller
2009-01-11 22:29         ` Mike Travis [this message]
2009-01-11 22:29           ` Mike Travis

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=496A72B3.8010105@sgi.com \
    --to=travis@sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@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 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.