From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Gao Xiang <gaoxiang25@huawei.com>, Chao Yu <yuchao0@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: "Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH] MAINTAINERS: add tree location for staging/erofs
Date: Sun, 9 Sep 2018 20:34:32 +0200 [thread overview]
Message-ID: <20180909183432.9752-1-linux@weissschuh.net> (raw)
In-Reply-To: <5c44a63b-041d-1fce-0748-53c0b44f5983@huawei.com>
Hi Chao, hi Gao,
On Sun, 2018-09-09T23:16+0800, Chao Yu wrote:
> Hi Thomas,
>
> On 2018/9/8 11:28, Gao Xiang wrote:
>> Hi Thomas,
>>
>> Thanks for your new patch.
>>
>> It seems that this patch also introduces 2 new 'WARNING: line over 80 characters',
>> could you please fix it in the patch?
@Chao,Gao: For some reason there seems to be a problem when receiving mails
from you. The one I received now was the first one from you that reached me
directly. Before I only got your messages in the quotes from Dan and now in the
quotes from the mail I am responding to.
(I will try to investigate the reason for this)
Sorry for my slow responses before.
> It will be better to fix that.
A new patch will shortly follow.
> Some reviewed cleanup patches are merged before this patch, then I failed to add
> this one, so could you rebase on top of erofs dev branch in below link:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=erofs
I was not aware of this tree and worked off of staging / next.
A patch is attached to this message that adds the tree to the MAINTAINERS file.
-- >8 --
Currently this location is not documented.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a5b256b25905..9087e0b74821 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13747,6 +13747,7 @@ F: drivers/staging/comedi/
STAGING - EROFS FILE SYSTEM
M: Gao Xiang <gaoxiang25@huawei.com>
M: Chao Yu <yuchao0@huawei.com>
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git erofs
L: linux-erofs@lists.ozlabs.org
S: Maintained
F: drivers/staging/erofs/
--
2.18.0
next prev parent reply other threads:[~2018-09-09 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180830205605.19492-1-linux@weissschuh.net>
2018-09-07 16:39 ` [PATCH v2] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-08 3:28 ` Gao Xiang
2018-09-09 15:16 ` Chao Yu
2018-09-09 18:34 ` Thomas Weißschuh [this message]
2018-09-10 3:56 ` [PATCH] MAINTAINERS: add tree location for staging/erofs Gao Xiang
2018-09-10 15:59 ` Chao Yu
2018-09-10 16:50 ` Gao Xiang
2018-09-10 19:41 ` [PATCH v4] staging: erofs: use explicit unsigned int type Thomas Weißschuh
2018-09-11 16:46 ` Chao Yu
2018-09-12 6:21 ` Gao Xiang
2018-09-13 16:46 ` Gao Xiang
2018-09-09 18:37 ` [PATCH v3] " Thomas Weißschuh
2018-09-10 8:10 ` Greg Kroah-Hartman
2018-09-10 19:15 ` Thomas Weißschuh
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=20180909183432.9752-1-linux@weissschuh.net \
--to=linux@weissschuh.net \
--cc=devel@driverdev.osuosl.org \
--cc=gaoxiang25@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.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