From: Mike Frysinger <vapier.adi@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Travis <travis@sgi.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jack Steiner <steiner@sgi.com>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bitmap, irq: Add smp_affinity_list interface to /proc/irq
Date: Thu, 31 Mar 2011 14:15:24 -0400 [thread overview]
Message-ID: <AANLkTinrDjgb9PSuWVjk+dTSp1Te0284MuMHWc+jL_bf@mail.gmail.com> (raw)
In-Reply-To: <20110331163916.2C6D.A69D9226@jp.fujitsu.com>
On Thu, Mar 31, 2011 at 03:37, KOSAKI Motohiro wrote:
>> > [If it was up to me, I'd eliminate the bitmask interfaces and just keep the
>> > list interfaces. That's the stupid interface that's not needed, and far more
>> > shortsighted.]
>>
>> Agree.
>>
>> It's not impossible to remove those interfaces. My preferred approach
>> is to add a once-per-boot warning printk if anyone uses the old
>> interface and to remove the thing altogether in three or five years.
>>
>> That reminds me. It's been like ten years. Someone please delete sys_bdflush().
>
> This?
>
> But to be honest, this long diffstat seems tell me the worth is doubious. ;-)
you dont need to update the arches. just leave the compat option in
kernel/sys_ni.c. there is really no overhead at runtime as the func
is aliased to the ENOSYS stub.
-mike
next prev parent reply other threads:[~2011-03-31 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 23:46 Mike Travis
2011-03-29 23:56 ` Andrew Morton
2011-03-30 0:43 ` Andrew Morton
2011-03-30 0:51 ` Mike Travis
2011-03-30 0:56 ` Andrew Morton
2011-03-30 0:58 ` Mike Travis
2011-03-30 1:04 ` Mike Travis
2011-03-30 1:13 ` Andrew Morton
2011-03-31 7:37 ` KOSAKI Motohiro
2011-03-31 18:15 ` Mike Frysinger [this message]
2011-03-30 1:12 ` 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=AANLkTinrDjgb9PSuWVjk+dTSp1Te0284MuMHWc+jL_bf@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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
all inboxes | Powered by JetHome®