From: Dimitri Sivanich <sivanich@hpe.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
Dimitri Sivanich <sivanich@sgi.com>,
Nate Zimmer <nzimmer@sgi.com>, Russ Anderson <rja@sgi.com>,
LKML <linux-kernel@vger.kernel.org>,
Mike Travis <mike.travis@hpe.com>
Cc: Dimitri Sivanich <sivanich@hpe.com>
Subject: Re: status of the Altix mmtimer driver
Date: Fri, 26 May 2017 08:05:34 -0500 [thread overview]
Message-ID: <20170526130534.GE30788@hpe.com> (raw)
In-Reply-To: <20170524003601.GB23931@hpe.com>
Note that the mmtimer struct can probably be removed from the k_itimer struct
in include/linux/posix-timers.h, just for completeness.
--- a/include/linux/posix-timers.h
+++ b/include/linux/posix-timers.h
@@ -73,12 +73,6 @@ struct k_itimer {
} real;
struct cpu_timer_list cpu;
struct {
- unsigned int clock;
- unsigned int node;
- unsigned long incr;
- unsigned long expires;
- } mmtimer;
- struct {
struct alarm alarmtimer;
ktime_t interval;
} alarm;
On Tue, May 23, 2017 at 07:36:01PM -0500, Dimitri Sivanich wrote:
> Since this is SN2 specific, this can be removed.
>
> On Tue, May 23, 2017 at 05:27:16PM +0200, Thomas Gleixner wrote:
> > On Tue, 23 May 2017, Christoph Hellwig wrote:
> >
> > Cc: + Mike
> >
> > > Hi folks,
> > >
> > > what's the status of the SGI support for the IA64 SN2-specific
> > > altic mmtimer (drivers/char/mmtimer.c)? It's the only driver that
> > > register a k_lock outside the core kernel, so if we could get rid of
> > > it because the remaining IA64 user are all on somewhat old distros
> > > anyway it would make our life a whole lot easier.
> > >
next prev parent reply other threads:[~2017-05-26 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 7:08 sttus of the Altix mmtimer driver Christoph Hellwig
2017-05-23 15:27 ` status " Thomas Gleixner
2017-05-24 0:36 ` Dimitri Sivanich
2017-05-26 13:05 ` Dimitri Sivanich [this message]
2017-05-27 11:04 ` [tip:timers/core] posix-timers: Remove mmtimer leftovers tip-bot for Dimitri Sivanich
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=20170526130534.GE30788@hpe.com \
--to=sivanich@hpe.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=nzimmer@sgi.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).