linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-mips@vger.kernel.org,
	"Maciej W . Rozycki" <macro@orcam.me.uk>,
	Tiezhu Yang <yangtiezhu@loongson.cn>, Willy Tarreau <w@1wt.eu>,
	linux-edac@vger.kernel.org, linux-hams@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arch: mips: update references to current linux-mips list
Date: Tue, 23 Feb 2021 13:29:28 +0100	[thread overview]
Message-ID: <20210223122928.GD7765@alpha.franken.de> (raw)
In-Reply-To: <20210222161905.1153-4-lukas.bulwahn@gmail.com>

On Mon, Feb 22, 2021 at 05:19:03PM +0100, Lukas Bulwahn wrote:
> The linux-mips mailing list now lives at kernel.org. Update all references
> in the kernel tree.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>  arch/mips/kernel/r4k-bugs64.c | 2 +-
>  arch/mips/lib/iomap-pci.c     | 2 +-
>  arch/mips/sgi-ip32/ip32-irq.c | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)

applied only this patch to mips-next.

For the other patches I'll wait for how the resolution for linux-mips.org
looks like.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  parent reply	other threads:[~2021-02-23 12:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 16:19 [PATCH 0/5] Remove dead linux-mips.org references Lukas Bulwahn
2021-02-22 16:19 ` [PATCH 1/5] MAINTAINERS: mark sections from Ralf Baechle orphan Lukas Bulwahn
2021-02-22 16:19 ` [PATCH 2/5] MAINTAINERS: remove linux-mips.org references Lukas Bulwahn
2021-02-23  1:16   ` Huacai Chen
2021-02-23  9:48   ` Philippe Mathieu-Daudé
2021-02-26  8:29     ` Lukas Bulwahn
2021-02-22 16:19 ` [PATCH 3/5] arch: mips: update references to current linux-mips list Lukas Bulwahn
2021-02-23  1:17   ` Huacai Chen
2021-02-23  9:49   ` Philippe Mathieu-Daudé
2021-02-23 12:29   ` Thomas Bogendoerfer [this message]
2021-02-23 13:24     ` Maciej W. Rozycki
2021-02-22 16:19 ` [PATCH 4/5] arch: mips: remove dead references Lukas Bulwahn
2021-02-23  1:19   ` Huacai Chen
2021-02-23  9:59   ` Philippe Mathieu-Daudé
2021-02-23 12:30     ` Maciej W. Rozycki
2021-02-22 16:19 ` [PATCH 5/5] MIPS: SGI-IP27: fix spelling in Copyright Lukas Bulwahn
2021-02-23  1:20   ` Huacai Chen
2021-02-23  9:50   ` Philippe Mathieu-Daudé
2021-02-23 12:33     ` Maciej W. Rozycki
2021-02-23 13:33       ` Philippe Mathieu-Daudé
2021-02-23 13:25   ` Maciej W. Rozycki
2021-02-22 17:47 ` [PATCH 0/5] Remove dead linux-mips.org references Maciej W. Rozycki
2021-02-22 17:56   ` Lukas Bulwahn
2021-02-22 18:19   ` [EXTERNAL]Re: " Kurt Martin
2021-03-22  7:52     ` Lukas Bulwahn
     [not found]       ` <BY5PR22MB18410B38B795973450A10D4DC7659@BY5PR22MB1841.namprd22.prod.outlook.com>
2021-03-23  3:36         ` Kurt Martin

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=20210223122928.GD7765@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=macro@orcam.me.uk \
    --cc=w@1wt.eu \
    --cc=yangtiezhu@loongson.cn \
    /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;
as well as URLs for NNTP newsgroup(s).