From: Christoph Hellwig <hch@lst.de>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: PATCH powerpc: Merge asm-ppc*/hardirq.h
Date: Wed, 14 Sep 2005 15:43:47 +0200 [thread overview]
Message-ID: <20050914134347.GB9700@lst.de> (raw)
In-Reply-To: <1126705294.14036.4.camel@cashmere.sps.mot.com>
On Wed, Sep 14, 2005 at 08:41:34AM -0500, Jon Loeliger wrote:
> > I'd suggest just using a DECLARE_PER_CPU variable for last_jiffy_stamp.
> > In facct I plan to get rid of irq_cpustat_t completely at some point.
>
> Hmmm... So, I don't want to mess that up. How about I leave it
> as I've suggested and leave that step up to you as a follow on?
ok.
next prev parent reply other threads:[~2005-09-14 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 20:38 PATCH powerpc: Merge asm-ppc*/hardirq.h Jon Loeliger
2005-09-14 11:05 ` Christoph Hellwig
2005-09-14 13:41 ` Jon Loeliger
2005-09-14 13:43 ` Christoph Hellwig [this message]
2005-09-16 15:45 ` PATCH powerpc: Revised merge asm-ppc*/hardirq.h Jon Loeliger
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=20050914134347.GB9700@lst.de \
--to=hch@lst.de \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).