From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Clemens Ladisch <clemens@ladisch.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] hpet: drop stale link
Date: Thu, 11 Feb 2016 01:08:38 +0200 [thread overview]
Message-ID: <20160211010529-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20160210131414.605e8eb6@lwn.net>
On Wed, Feb 10, 2016 at 01:14:14PM -0700, Jonathan Corbet wrote:
> On Mon, 1 Feb 2016 13:32:56 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > Looks like the HPET spec at intel.com got moved.
> > It isn't hard to find so drop the link, just mention
> > the revision assumed.
>
> Hmm...what I see suggests this patch doesn't do that...
>
> > - * http://www.intel.com/hardwaredesign/hpetspec_1.pdf
> > + * http://www.intel.com/content/dam/www/public/us/en/documents/technical-specifications/software-developers-hpet-spec-1-0a.pdf
> >
>
> ..?
>
> jon
Did it again: edit code, run git commit --amend and edited commit log
but forgot -a so new code didn't get included in the commit,
run git format-patch and then send-email without reviewing the
result :(
Sorry about that - posted v2 which does what it says.
--
MST
prev parent reply other threads:[~2016-02-10 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 11:32 [PATCH] hpet: drop stale link Michael S. Tsirkin
2016-02-03 10:53 ` Ingo Molnar
2016-02-03 11:54 ` Michael S. Tsirkin
2016-02-10 20:14 ` Jonathan Corbet
2016-02-10 23:08 ` Michael S. Tsirkin [this message]
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=20160211010529-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=arnd@arndb.de \
--cc=clemens@ladisch.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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