public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
	<jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] rdma: Add Jason as a co-maintainer
Date: Fri, 17 Nov 2017 17:54:34 +0000	[thread overview]
Message-ID: <1510941272.2846.46.camel@wdc.com> (raw)
In-Reply-To: <20171116204400.GA28216-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

[-- 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š

  parent reply	other threads:[~2017-11-17 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 20:44 [PATCH] rdma: Add Jason as a co-maintainer Jason Gunthorpe
2017-11-17  5:00 ` Leon Romanovsky
     [not found] ` <20171116204400.GA28216-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-17 17:54   ` Bart Van Assche [this message]
     [not found]     ` <1510941272.2846.46.camel-Sjgp3cTcYWE@public.gmane.org>
2017-11-17 18:14       ` Jason Gunthorpe
     [not found]         ` <20171117181410.GL4276-uk2M96/98Pc@public.gmane.org>
2017-11-17 19:45           ` Doug Ledford
     [not found]             ` <1510947901.3973.26.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-17 21:32               ` Jason Gunthorpe
     [not found]                 ` <20171117213227.GQ4276-uk2M96/98Pc@public.gmane.org>
2017-11-18  1:44                   ` Doug Ledford
2017-11-18  7:26                     ` Leon Romanovsky
2017-11-19  8:33       ` Amrani, Ram
2017-11-20 16:10   ` Leon Romanovsky
2017-11-20 18:06     ` Jason Gunthorpe
     [not found]       ` <20171120180631.GE626-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-21  5:04         ` Leon Romanovsky
     [not found]           ` <20171121050456.GM18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-21  6:37             ` Leon Romanovsky
2017-11-20 12:45 ` Sagi Grimberg

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=1510941272.2846.46.camel@wdc.com \
    --to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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