public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ISA DMA suspend for x86_64
Date: Sat, 2 Jul 2005 19:40:55 +0200	[thread overview]
Message-ID: <20050702174055.GI21330@wotan.suse.de> (raw)
In-Reply-To: <42C6CF40.4040308@drzeus.cx>

> I used i8259.c as an example and it includes its suspend routines in all
> cases. Also, the problem this patch solves is for suspend-to-ram, not
> suspend-to-disk (i.e. software suspend).

Hmm, it would be better if that all was CONFIG_ able. But ok.

> Index: linux-wbsd/arch/x86_64/kernel/Makefile
> ===================================================================
> --- linux-wbsd/arch/x86_64/kernel/Makefile	(revision 153)
> +++ linux-wbsd/arch/x86_64/kernel/Makefile	(working copy)
> @@ -7,7 +7,8 @@
>  obj-y	:= process.o semaphore.o signal.o entry.o traps.o irq.o \
>  		ptrace.o time.o ioport.o ldt.o setup.o i8259.o sys_x86_64.o \
>  		x8664_ksyms.o i387.o syscall.o vsyscall.o \
> -		setup64.o bootflag.o e820.o reboot.o quirks.o
> +		setup64.o bootflag.o e820.o reboot.o quirks.o \
> +		../../i386/kernel/i8237.o

I think that will break in builds with separate objdirs. You'll need
to do it like the other files (see the end of the Makefile)

-Andi

  reply	other threads:[~2005-07-02 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42987450.9000601@drzeus.cx.suse.lists.linux.kernel>
     [not found] ` <1117288285.2685.10.camel@localhost.localdomain.suse.lists.linux.kernel>
     [not found]   ` <42A2B610.1020408@drzeus.cx.suse.lists.linux.kernel>
     [not found]     ` <42A3061C.7010604@drzeus.cx.suse.lists.linux.kernel>
     [not found]       ` <42B1A08B.8080601@drzeus.cx.suse.lists.linux.kernel>
     [not found]         ` <20050616170622.A1712@flint.arm.linux.org.uk.suse.lists.linux.kernel>
     [not found]           ` <42C3A698.9020404@drzeus.cx.suse.lists.linux.kernel>
     [not found]             ` <1120130926.6482.83.camel@localhost.localdomain.suse.lists.linux.kernel>
     [not found]               ` <42C3E3A4.3090305@drzeus.cx.suse.lists.linux.kernel>
     [not found]                 ` <42C432BB.407@drzeus.cx.suse.lists.linux.kernel>
2005-07-01 10:53                   ` [PATCH 2/2] ISA DMA suspend for x86_64 Andi Kleen
2005-07-01 19:30                     ` Adam Belay
2005-07-02 17:30                     ` Pierre Ossman
2005-07-02 17:40                       ` Andi Kleen [this message]
2005-07-02 17:50                         ` Pierre Ossman
2005-07-02 18:27                           ` Andi Kleen
2005-07-02 22:04                             ` Pierre Ossman
2005-07-03 15:03                               ` Andi Kleen
2005-07-03 11:39                         ` Pavel Machek
2005-05-28 13:38 ISA DMA controller hangs Pierre Ossman
2005-05-28 13:51 ` Alan Cox
2005-06-05  8:21   ` Pierre Ossman
2005-06-05 14:03     ` Pierre Ossman
2005-06-16 15:53       ` Pierre Ossman
2005-06-16 16:06         ` Russell King
2005-06-30  8:00           ` Pierre Ossman
2005-06-30 11:28             ` Alan Cox
2005-06-30 12:20               ` Pierre Ossman
2005-06-30 17:58                 ` [PATCH 2/2] ISA DMA suspend for x86_64 Pierre Ossman

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=20050702174055.GI21330@wotan.suse.de \
    --to=ak@suse.de \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.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