From: Moritz Fischer <mdf@kernel.org>
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>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] MAINTAINERS: Update linux-fpga repository location
Date: Tue, 19 Apr 2022 21:39:10 -0700 [thread overview]
Message-ID: <Yl+ObpM2d2wuJfkY@archbook> (raw)
In-Reply-To: <20220408022002.22957-1-mdf@kernel.org>
On Thu, Apr 07, 2022 at 07:20:02PM -0700, Moritz Fischer 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?
>
> Thanks,
>
> Moritz
> ---
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fd768d43e048..9b08d5ea001e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7717,7 +7717,7 @@ R: Tom Rix <trix@redhat.com>
> L: linux-fpga@vger.kernel.org
> S: Maintained
> Q: http://patchwork.kernel.org/project/linux-fpga/list/
> -T: git git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga.git
> F: Documentation/devicetree/bindings/fpga/
> F: Documentation/driver-api/fpga/
> F: Documentation/fpga/
> --
> 2.35.1
>
Applied to for-next,
- Moritz
prev parent reply other threads:[~2022-04-20 4:40 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
2022-04-20 4:39 ` Moritz Fischer [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=Yl+ObpM2d2wuJfkY@archbook \
--to=mdf@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).