From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>,
Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: get_maintainer.pl bug?
Date: Thu, 25 Jan 2018 10:53:29 -0500 [thread overview]
Message-ID: <1516895609.27592.126.camel@redhat.com> (raw)
In-Reply-To: <20180124162802.GB16845-uk2M96/98Pc@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On Wed, 2018-01-24 at 09:28 -0700, Jason Gunthorpe wrote:
> On Wed, Jan 24, 2018 at 01:54:45PM +0200, Leon Romanovsky wrote:
> > On Wed, Jan 24, 2018 at 01:23:24PM +0200, Yuval Shaia wrote:
> > > Hi,
> > > This is what i get when running scripts/get_maintainer.pl drivers/infiniband/:
> > >
> > > Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> (supporter:INFINIBAND SUBSYSTEM)
> > > Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org> (supporter:INFINIBAND SUBSYSTEM)
> > > linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org (open list:INFINIBAND SUBSYSTEM)
> > > linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org (open list)
> > >
> > > However section "INFINIBAND SUBSYSTEM" pointed out a different address for
> > > Jason:
> > >
> > > INFINIBAND SUBSYSTEM
> > > M: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > > M: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > > L: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > > W: http://www.openfabrics.org/
> > > Q: http://patchwork.kernel.org/project/linux-rdma/list/
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git
^^^^^^^^
This is wrong though. We need to update that. I'll fix that right
now.
> > > S: Supported
> > > F: Documentation/devicetree/bindings/infiniband/
> > > F: Documentation/infiniband/
> > > F: drivers/infiniband/
> > > F: include/uapi/linux/if_infiniband.h
> > > F: include/uapi/rdma/
> > > F: include/rdma/
> > >
> > > So
> > > - Which one is the correct one?
> > > - What am i doing wrong when using scripts/get_maintainer.pl?
> >
> > Both are correct, and the jgg-uk2M96/98Pc@public.gmane.org email is taken from .mailmap
> > file.
>
> Yes, I prefer the ziepe one for bulk/automatic sorts of email, that is
> why it is in the mailamp.
>
> Thanks,
> Jason
>
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-25 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 11:23 get_maintainer.pl bug? Yuval Shaia
2018-01-24 11:54 ` Leon Romanovsky
[not found] ` <20180124115445.GH1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-24 12:33 ` Jonathan Toppins
2018-01-24 16:28 ` Jason Gunthorpe
[not found] ` <20180124162802.GB16845-uk2M96/98Pc@public.gmane.org>
2018-01-25 15:53 ` Doug Ledford [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=1516895609.27592.126.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.