All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Jung <ralfjung-e@gmx.de>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86, ioapic: Reserve only 128 bytes for IOAPICs
Date: Fri, 26 Aug 2011 11:53:20 +0200	[thread overview]
Message-ID: <201108261153.21103.ralfjung-e@gmx.de> (raw)
In-Reply-To: <20110826093917.GE3903@sun>

Hi,


> Hi Ralf, I can't put that risk on you. Hell knows how it will react
> on such reprogramming (which is seems rather a bios duty than kernel).
Oh, we are talking about that kind of problems? It's my main (and only) work 
laptop, so... thanks for the warning ;-)

Kind regards,
Ralf

  reply	other threads:[~2011-08-26  9:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 23:05 [PATCH 1/2] x86, ioapic: Reserve only 128 bytes for IOAPICs Bjorn Helgaas
2011-08-25 23:05 ` [PATCH 2/2] x86, ioapic: Announce resources reserved " Bjorn Helgaas
2011-08-25 23:33 ` [PATCH 1/2] x86, ioapic: Reserve only 128 bytes " Suresh Siddha
2011-08-26  0:17   ` Bjorn Helgaas
2011-08-26  1:41     ` H. Peter Anvin
2011-08-26  6:18       ` Yinghai Lu
2011-08-26  6:48       ` Cyrill Gorcunov
2011-08-26  9:22         ` Ralf Jung
2011-08-26  9:39           ` Cyrill Gorcunov
2011-08-26  9:53             ` Ralf Jung [this message]
2011-08-26  9:56               ` Cyrill Gorcunov
2011-08-26  6:22     ` Cyrill Gorcunov
2011-08-26 16:21       ` Bjorn Helgaas
2011-08-26 16:24         ` H. Peter Anvin
2011-08-26 18:09         ` Cyrill Gorcunov
2011-08-26 18:21           ` H. Peter Anvin
2011-08-26 19:15             ` Cyrill Gorcunov
     [not found] ` <CAErSpo5kEw=VTVv-=_D3hQg5oRNL9yEyJUnpP0biH=t3WRXMZw@mail.gmail.com>
2011-08-26 21:09   ` Fwd: " Ralf Jung

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=201108261153.21103.ralfjung-e@gmx.de \
    --to=ralfjung-e@gmx.de \
    --cc=bhelgaas@google.com \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.