From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 19 (new CONFIG_NUMA_MIGRATE_IRQ_DESC option)
Date: Fri, 19 Dec 2008 22:42:21 +0100 [thread overview]
Message-ID: <20081219214221.GE2351@elte.hu> (raw)
In-Reply-To: <494C0D28.6040002@kernel.org>
* Yinghai Lu <yinghai@kernel.org> wrote:
> > +++ b/kernel/irq/numa_migrate.c
> > @@ -0,0 +1,127 @@
> > +/*
> > + * linux/kernel/irq/handle.c
> > + *
> > + * Copyright (C) 1992, 1998-2006 Linus Torvalds, Ingo Molnar
> > + * Copyright (C) 2005-2006, Thomas Gleixner, Russell King
> > + *
> > + * This file contains the core interrupt handling code.
> > + *
> > + * Detailed information is available in Documentation/DocBook/genericirq
> > + *
> > + */
> >
> > hmmm? ;-)
>
> seperated from irq/handle.c
>
> oh, will remove those lines.
Yeah, replace them with something like:
/*
* NUMA irq-desc migration code
*
* Migrate IRQ data structures (irq_desc, chip_data, etc.) over to
* the new "home node" of the IRQ.
*/
Ingo
next prev parent reply other threads:[~2008-12-19 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 12:57 linux-next: Tree for December 19 Stephen Rothwell
2008-12-19 21:01 ` linux-next: Tree for December 19 (new CONFIG_NUMA_MIGRATE_IRQ_DESC option) Bartlomiej Zolnierkiewicz
2008-12-19 21:07 ` Yinghai Lu
2008-12-19 21:42 ` Ingo Molnar [this message]
2008-12-19 21:48 ` [PATCH] sparseirq: fix numa_migrate_irq_desc dependency and comments Yinghai Lu
2008-12-19 21:57 ` Ingo Molnar
2008-12-19 21:40 ` linux-next: Tree for December 19 (new CONFIG_NUMA_MIGRATE_IRQ_DESC option) Ingo Molnar
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=20081219214221.GE2351@elte.hu \
--to=mingo@elte.hu \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yinghai@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 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).