From: Jonathan Corbet <corbet@lwn.net>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Cooper <amc96@cam.ac.uk>, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/ia64: Drop obsolete Xen documentation
Date: Mon, 31 Aug 2020 22:16:29 +0000 [thread overview]
Message-ID: <20200831161629.2dc218ff@lwn.net> (raw)
In-Reply-To: <20200827175405.24344-1-andrew.cooper3@citrix.com>
On Thu, 27 Aug 2020 18:54:05 +0100
Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> While the xensource.com URLs referenced still exist, neither the Xen or Linux
> 2.6.18 fork have been touched since 2009, 11 years ago. Other URLs are dead.
>
> IA64 support was removed in Xen 4.2, in 2012. Relegate this piece of
> documentation to source history.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Applied, thanks.
jon
prev parent reply other threads:[~2020-08-31 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 17:54 [PATCH] docs/ia64: Drop obsolete Xen documentation Andrew Cooper
2020-08-31 22:16 ` Jonathan Corbet [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=20200831161629.2dc218ff@lwn.net \
--to=corbet@lwn.net \
--cc=amc96@cam.ac.uk \
--cc=andrew.cooper3@citrix.com \
--cc=fenghua.yu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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