From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
"paulburton@kernel.org" <paulburton@kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Replace HTTP links with HTTPS ones
Date: Thu, 16 Jul 2020 15:56:05 +0200 [thread overview]
Message-ID: <20200716135605.GA15355@alpha.franken.de> (raw)
In-Reply-To: <CAHiYmc7ax=A=Tb59wh4+yHx=2MEKc3G==tun5nsefbKvsceBHg@mail.gmail.com>
On Wed, Jul 15, 2020 at 12:07:55PM +0200, Aleksandar Markovic wrote:
> On Tuesday, July 14, 2020, Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
> > 在 2020/7/13 16:52, Alexander A. Klimov 写道:
> >> virtual processors which supports SMP. This is equivalent to the
> >> Intel Hyperthreading feature. For further information go to
> >> - <http://www.imgtec.com/mips/mips-multithreading.asp>.
> >> + <https://www.imgtec.com/mips/mips-multithreading.asp>.
> >>
> >
> > All MIPS content have been removed from IMGTEC's site, we'd better remove
> > this link?
> >
> >
> Perhaps it is better to replace it with:
>
> https://www.mips.com/products/architectures/ase/multi-threading/
>
> ?
yes, looks better.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-07-16 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 8:52 [PATCH] MIPS: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-14 6:45 ` Jiaxun Yang
2020-07-14 19:12 ` [PATCH] mips: " Alexander A. Klimov
2020-07-16 9:55 ` Thomas Bogendoerfer
[not found] ` <CAHiYmc7ax=A=Tb59wh4+yHx=2MEKc3G==tun5nsefbKvsceBHg@mail.gmail.com>
2020-07-16 13:56 ` Thomas Bogendoerfer [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=20200716135605.GA15355@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=grandmaster@al2klimov.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@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