From: Nathan Zimmer <nzimmer@sgi.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
Christoph Lameter <cl@linux.com>, <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, <hpa@zytor.com>,
<tj@kernel.org>, <mingo@kernel.org>,
<linux-tip-commits@vger.kernel.org>,
Alex Thorlton <athorlton@sgi.com>, <travis@sgi.com>
Subject: Re: [tip:x86/platform] x86/uv/time: Migrate to new set-state interface
Date: Wed, 5 Aug 2015 09:29:20 -0500 [thread overview]
Message-ID: <55C21DC0.7000302@sgi.com> (raw)
In-Reply-To: <20150805051548.GD15655@linux>
Yes, thank you for the correction.
On 08/05/2015 12:15 AM, Viresh Kumar wrote:
> On 04-08-15, 10:25, Nathan Zimmer wrote:
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 907ce01..9c2beb3 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10885,6 +10885,15 @@ W: http://en.wikipedia.org/wiki/Util-linux
>> T: git git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
>> S: Maintained
>>
>> +UV PLATFORM
>> +M: Mike Travis <travis@sgi.com>
>> +M: uv_kernel@sgi.com
> Should that be L:, as it looks to be a list?
>
>> +S: Supported
>> +F: arch/x86/kernel/apic/x2apic_uv_x.c
>> +F: arch/x86/platform/uv/
>> +F: arch/x86/include/asm/uv/
>> +F: drivers/char/uv_mmtimer.c
>> +
>> UVESAFB DRIVER
>> M: Michal Januszewski <spock@gentoo.org>
>> L: linux-fbdev@vger.kernel.org
>> --
>> 1.8.2.1
>>
>
next prev parent reply other threads:[~2015-08-05 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 10:58 [PATCH 0/5] X86: Migrate clockevent drivers to 'set-state' interface Viresh Kumar
2015-07-16 10:58 ` [PATCH 1/5] x86/apic: Migrate to new " Viresh Kumar
2015-07-30 19:27 ` [tip:x86/apic] x86/apic: Migrate apic timer to new set_state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 2/5] x86/hpet: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:30 ` [tip:x86/core] x86/hpet: Migrate to new set_state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 3/5] x86/lguest/timer: Migrate to new 'set-state' interface Viresh Kumar
2015-07-16 11:59 ` Rusty Russell
2015-07-30 19:28 ` [tip:x86/platform] x86/lguest/timer: Migrate to new set-state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 4/5] x86/uv/time: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:28 ` [tip:x86/platform] x86/uv/time: Migrate to new set-state interface tip-bot for Viresh Kumar
2015-07-30 20:04 ` Christoph Lameter
2015-07-30 22:25 ` Thomas Gleixner
2015-07-31 5:21 ` Viresh Kumar
2015-07-31 12:20 ` Dimitri Sivanich
2015-08-04 15:25 ` Nathan Zimmer
2015-08-05 5:15 ` Viresh Kumar
2015-08-05 14:29 ` Nathan Zimmer [this message]
2015-07-16 10:58 ` [PATCH 5/5] x86/xen/time: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:28 ` [tip:x86/platform] x86/xen/time: Migrate to new set-state interface tip-bot for Viresh Kumar
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=55C21DC0.7000302@sgi.com \
--to=nzimmer@sgi.com \
--cc=athorlton@sgi.com \
--cc=cl@linux.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=travis@sgi.com \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).