Re: [PATCH] rdma: Add Jason as a co-maintainer

Bart Van Assche
2017-11-17T17:54:34Z

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2404 bytes --]

On Thu, 2017-11-16 at 13:44 -0700, Jason Gunthorpe wrote:
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7f9c4f3fc9419d..d4e621e350f2cf 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6827,6 +6827,7 @@ F: drivers/ipack/
>
> INFINIBAND SUBSYSTEM
> M: Doug Ledford <dledford@redhat.com>
> +M: Jason Gunthorpe <jgg@mellanox.com>
> L: linux-rdma@vger.kernel.org
> W: http://www.openfabrics.org/
> Q: http://patchwork.kernel.org/project/linux-rdma/list/

Hello Doug and Jason,

Thanks Doug for having added a co-maintainer. Jason, thank you for willing
to be a co-maintainer.

Jason, if you are going to send pull requests to Linus you should be aware
of the following:
* Linus trusts pull requests from a kernel.org repository more than pull
requests from a repository outside kernel.org (e.g. github). Any requests
to pull from e.g. github must be PGP-signed.
* If you send an e-mail to Wu Fengguang then he will add a branch from your
repository to his zero-day testing. This is a great way to catch build
failures before linux-next catches these.
* Any patches that will be sent to Linus must have been in the for-next
repository for at least a few days. Requests to add a branch to linux-next
should be sent to Stephen Rothwell with linux-next in Cc.
* Maintainers are expected to keep an eye on merge conflicts and other reports
sent out to the linux-next mailing list
(http://vger.kernel.org/vger-lists.html#linux-next).
* Rebasing a tree that will be sent to Linus is completely inacceptable. A
quote from Linus: "And in general, you simply should never rebase commits
that have already been publicized." Source: Linus Torvalds, Re: linux-next:
Signed-off-by missing for commit in the drivers-x86 tree, linux-next mailing
list, 2 August 2017 (https://www.spinics.net/lists/kernel/msg2571584.html).
* Backmerging (merging a later rc into a maintainer tree) to pull in rc fixes
from other maintainers is considered inacceptable too. If patches from other
maintainers are really needed I think it is acceptable to merge a maintainer
tree into Linus' tree and to apply late rc patches on top of that merged
tree.

See also https://lwn.net/Articles/328436/.

Best regards,

Bart.N‹§²æìr¸›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±­ÙšŠ{ayº\x1dÊ‡Ú™ë,j\a­¢f£¢·hš‹»öì\x17/oSc¾™Ú³9˜uÀ¦æå‰È&jw¨®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þ–Šàþf£¢·hšˆ§~ˆmš