From: Frank Schaefer <fschaefer.oss@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] x86: add HPET-quirk for nVidia MCP61 LPC Bridge (10de:03e0)
Date: Sat, 20 Mar 2010 13:53:01 +0100 [thread overview]
Message-ID: <4BA4C52D.6020607@googlemail.com> (raw)
In-Reply-To: <4BA3A517.4010307@ladisch.de>
Clemens Ladisch schrieb:
> Frank Schaefer wrote:
>
>> Any comments on this patch ?
>>
> Gmail ate your tabs; see Documentation/email-clients.txt.
>
Thanks for your reply Clemens.
It wasn't Gmails fault, I made a pasting mistake...sorry.
> Cosmetic changes to not belong in the stable tree; see
> Documentation/stable_kernel_rules.txt.
>
Alright, no Cc stable.
>> Wrong list ?
>>
>
> arch/x86 stuff should go to <x86@kernel.org>.
>
>
> Regards,
> Clemens
>
The get-maintainer-script told me to send it to this list. Shouldn't it
be updated then ?
Also: this list seems to be mentioned nowhere, at least not at
http://www.linux.org/docs/lists.html
http://vger.kernel.org/vger-lists.html
Regards,
Frank
next prev parent reply other threads:[~2010-03-20 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 15:20 [PATCH][RESEND] x86: add HPET-quirk for nVidia MCP61 LPC Bridge (10de:03e0) Frank Schaefer
2010-03-19 16:23 ` Clemens Ladisch
2010-03-20 12:53 ` Frank Schaefer [this message]
2010-03-22 8:32 ` Clemens Ladisch
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=4BA4C52D.6020607@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--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