From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
Xu Yilun <yilun.xu@intel.com>, Wu Hao <hao.wu@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: Update linux-fpga repository location
Date: Thu, 21 Apr 2022 07:33:57 +1000 [thread overview]
Message-ID: <20220421073357.07bb69ec@canb.auug.org.au> (raw)
In-Reply-To: <Yl+KW2BfkEYXeQz8@archbook>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Hi Moritz,
On Tue, 19 Apr 2022 21:21:47 -0700 Moritz Fischer <mdf@kernel.org> wrote:
>
> On Sat, Apr 09, 2022 at 03:47:39PM +1000, Stephen Rothwell wrote:
> > Hi Moritz,
> >
> > On Thu, 7 Apr 2022 19:20:02 -0700 Moritz Fischer <mdf@kernel.org> wrote:
> > >
> > > As maintainer team we have decided to move the linux-fpga development
> > > to a shared repository with shared access.
> > >
> > > Cc: Xu Yilun <yilun.xu@intel.com>
> > > Cc: Wu Hao <hao.wu@intel.com>
> > > Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Signed-off-by: Moritz Fischer <mdf@kernel.org>
> > > ---
> > >
> > > Hi Stephen,
> > >
> > > can you help us update the linux-next part accordingly?
> >
> > I have done so, but you forgot to create the "fixes" branch in the new
> > tree. Also, did you want more contacts listed for the tree (apart from
> > yourself)?
>
> Fixed. Thanks!
>
> If you could add Xu Yilun and Wu Hao as contacts that'd be great!
Done.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-20 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 2:20 [PATCH] MAINTAINERS: Update linux-fpga repository location Moritz Fischer
2022-04-09 5:47 ` Stephen Rothwell
2022-04-20 4:21 ` Moritz Fischer
2022-04-20 21:33 ` Stephen Rothwell [this message]
2022-04-20 4:39 ` Moritz Fischer
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=20220421073357.07bb69ec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=yilun.xu@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;
as well as URLs for NNTP newsgroup(s).