linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Rob Herring <robh@kernel.org>
Subject: Re: linux-next: build warning after merge of the mips tree
Date: Fri, 31 Jul 2020 08:39:28 +1000	[thread overview]
Message-ID: <20200731083928.47bc96f0@canb.auug.org.au> (raw)
In-Reply-To: <e8757bd7-e6e6-5181-ef52-7dca0a114360@flygoat.com>

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

Hi all,

On Thu, 30 Jul 2020 09:56:59 +0800 Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
> 在 2020/7/30 上午9:40, Stephen Rothwell 写道:
> >
> > On Thu, 30 Jul 2020 09:04:40 +0800 Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:  
> >> Btw: Neither James nor Ralf is still active at Linux-MIPS.  
> > Interesting.  I have just them listed as my contacts for MIPS.  Should
> > I change to just Thomes (Thomas Bogendoerfer
> > <tsbogend@alpha.franken.de>)?  
> 
> Yes, Thomas is now the sole maintainer of Linux-MIPS.

OK, done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-30 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 10:31 linux-next: build warning after merge of the mips tree Stephen Rothwell
2020-07-30  1:04 ` Jiaxun Yang
2020-07-30  1:40   ` Stephen Rothwell
2020-07-30  1:56     ` Jiaxun Yang
2020-07-30 22:39       ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-20 23:43 Stephen Rothwell
2011-08-22  0:48 ` Stephen Rothwell
2011-08-24 23:18   ` Stephen Rothwell

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=20200731083928.47bc96f0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jhogan@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).