From: Thomas Gleixner <tglx@linutronix.de>
To: Edouard Gomez <ed.gomez@free.fr>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Thomas Backlund <tmb@mandriva.org>,
Leann Ogasawara <leann.ogasawara@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Dell Precision WorkStation 690 reboot quirk
Date: Wed, 8 Dec 2010 17:27:44 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1012081701130.2653@localhost6.localdomain6> (raw)
In-Reply-To: <4d8b4b3a1d3c6034b868.1291822674@egomez.in.mobiclip.com>
On Wed, 8 Dec 2010, Edouard Gomez wrote:
> # HG changeset patch
> # User Edouard Gomez <ed.gomez@free.fr>
> # Date 1291821505 -3600
> # Node ID 4d8b4b3a1d3c6034b86889fac38dd53e6579bb42
> # Parent 53e51000d59963c8ca408db4db619d2c82374c5e
> x86: Dell Precision WorkStation 690 reboot quirk
>
> This Dell workstation gets stuck on reboot unless booted with
> the paremeter reboot=bios.
>
> This patch has been submitted 3 times already to X86 ARCHITECTURE
> maintainers w/o any feedback so far. Trying my chance on the LKML.
Sorry, but I haven't seen this patch in my inbox and my mail server
log has only a single connection attempt to deliver mail from you on
Dec. 8 which ended up in one of my spam traps.
Cc'ing LKML (or some other relevant mailinglist) is recommended for
sending patches anyway. Documentation/SubmittingPatches says:
Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
Thanks,
tglx
next prev parent reply other threads:[~2010-12-08 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 15:37 Edouard Gomez
2010-12-08 16:27 ` Thomas Gleixner [this message]
2010-12-09 15:16 ` Matthew Garrett
2010-12-09 15:19 ` H. Peter Anvin
2010-12-09 15:27 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2010-03-05 15:55 Edouard Gomez
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=alpine.LFD.2.00.1012081701130.2653@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=ed.gomez@free.fr \
--cc=hpa@zytor.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tmb@mandriva.org \
--cc=x86@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
all inboxes | Powered by JetHome®