From: Luis de Bethencourt <luisbg@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
mchehab@kernel.org, hans.verkuil@cisco.com, mcgrof@kernel.org,
boris.brezillon@free-electrons.com, stefan@osg.samsung.com,
mkl@pengutronix.de, Luis de Bethencourt <luisbg@kernel.org>
Subject: [PATCH] MAINTAINERS: move the befs tree to kernel.org
Date: Sun, 9 Jul 2017 12:00:12 +0100 [thread overview]
Message-ID: <20170709110012.2991-1-luisbg@kernel.org> (raw)
Updating the location of the befs git tree and my email address.
Signed-off-by: Luis de Bethencourt <luisbg@kernel.org>
---
Hello,
The currently listed email address isn't valid anymore due to a job change.
It felt like a good moment to request a kernel.org account (thanks Konstantin
for the prompt response and easy instructions), and move both the git tree and
email address for kernel happy hacking.
Thanks,
Luis
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 75ac9dc..f9d6bda 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2504,10 +2504,10 @@ S: Supported
F: drivers/media/platform/sti/delta
BEFS FILE SYSTEM
-M: Luis de Bethencourt <luisbg@osg.samsung.com>
+M: Luis de Bethencourt <luisbg@kernel.org>
M: Salah Triki <salah.triki@gmail.com>
S: Maintained
-T: git git://github.com/luisbg/linux-befs.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/luisbg/linux-befs.git
F: Documentation/filesystems/befs.txt
F: fs/befs/
--
2.9.4
next reply other threads:[~2017-07-09 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 11:00 Luis de Bethencourt [this message]
2017-07-12 8:10 ` [PATCH] MAINTAINERS: move the befs tree to kernel.org Luis de Bethencourt
2017-07-12 21:40 ` Luis R. Rodriguez
2017-07-12 22:00 ` Andrew Morton
2017-07-14 8:07 ` Luis de Bethencourt
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=20170709110012.2991-1-luisbg@kernel.org \
--to=luisbg@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@kernel.org \
--cc=mkl@pengutronix.de \
--cc=stefan@osg.samsung.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).