From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Jani Nikula <jani.nikula@intel.com>
Cc: zwisler@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Mon, 26 Nov 2018 07:55:10 -0800 [thread overview]
Message-ID: <52ff06c49ec35599b3c8edf3bd3d1acbb9397c91.camel@perches.com> (raw)
In-Reply-To: <20181126091229.04b5dce0@coco.lan>
On Mon, 2018-11-26 at 09:12 -0200, Mauro Carvalho Chehab wrote:
> Hi Jani,
>
> Em Tue, 20 Nov 2018 10:10:25 +0200
> Jani Nikula <jani.nikula@intel.com> escreveu:
>
> > On Sun, 18 Nov 2018, Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > > Hmm.. Perhaps the subsystem profile should point to IRC channels if any?
> > > Several subsystems use them in order to provide newbies some directions
> > > and to discuss other development issues.
> >
> > MAINTAINERS:
> >
> > C: URI for chat protocol, server and channel where developers
> > usually hang out, for example irc://server/channel.
> >
> > Alas very few subsystems have added that.
> >
> > I actually fear very few subsystems will add a subsystem profile for
> > that matter.
>
> Sorry for a late reply. In the case of the media subsystem, we
> actually use 2 different channels, one when the matter is related
> to digital TV (#linuxtv) and another one for the rest (#v4l), both
> at freenode.
>
> That's something that wouldn't fit well into MAINTAINERS file, as
> we can't explain what should be used for each.
>
> So, the way it is it won't work well for us.
So maybe add a comment to both like:
C: <URI1> # only for digital tv #linuxtv
C: <URI2> # everything else
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Jani Nikula <jani.nikula@intel.com>
Cc: zwisler@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Mon, 26 Nov 2018 07:55:10 -0800 [thread overview]
Message-ID: <52ff06c49ec35599b3c8edf3bd3d1acbb9397c91.camel@perches.com> (raw)
In-Reply-To: <20181126091229.04b5dce0@coco.lan>
On Mon, 2018-11-26 at 09:12 -0200, Mauro Carvalho Chehab wrote:
> Hi Jani,
>
> Em Tue, 20 Nov 2018 10:10:25 +0200
> Jani Nikula <jani.nikula@intel.com> escreveu:
>
> > On Sun, 18 Nov 2018, Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > > Hmm.. Perhaps the subsystem profile should point to IRC channels if any?
> > > Several subsystems use them in order to provide newbies some directions
> > > and to discuss other development issues.
> >
> > MAINTAINERS:
> >
> > C: URI for chat protocol, server and channel where developers
> > usually hang out, for example irc://server/channel.
> >
> > Alas very few subsystems have added that.
> >
> > I actually fear very few subsystems will add a subsystem profile for
> > that matter.
>
> Sorry for a late reply. In the case of the media subsystem, we
> actually use 2 different channels, one when the matter is related
> to digital TV (#linuxtv) and another one for the rest (#v4l), both
> at freenode.
>
> That's something that wouldn't fit well into MAINTAINERS file, as
> we can't explain what should be used for each.
>
> So, the way it is it won't work well for us.
So maybe add a comment to both like:
C: <URI1> # only for digital tv #linuxtv
C: <URI2> # everything else
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Jani Nikula <jani.nikula@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
zwisler@kernel.org
Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile
Date: Mon, 26 Nov 2018 07:55:10 -0800 [thread overview]
Message-ID: <52ff06c49ec35599b3c8edf3bd3d1acbb9397c91.camel@perches.com> (raw)
In-Reply-To: <20181126091229.04b5dce0@coco.lan>
On Mon, 2018-11-26 at 09:12 -0200, Mauro Carvalho Chehab wrote:
> Hi Jani,
>
> Em Tue, 20 Nov 2018 10:10:25 +0200
> Jani Nikula <jani.nikula@intel.com> escreveu:
>
> > On Sun, 18 Nov 2018, Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > > Hmm.. Perhaps the subsystem profile should point to IRC channels if any?
> > > Several subsystems use them in order to provide newbies some directions
> > > and to discuss other development issues.
> >
> > MAINTAINERS:
> >
> > C: URI for chat protocol, server and channel where developers
> > usually hang out, for example irc://server/channel.
> >
> > Alas very few subsystems have added that.
> >
> > I actually fear very few subsystems will add a subsystem profile for
> > that matter.
>
> Sorry for a late reply. In the case of the media subsystem, we
> actually use 2 different channels, one when the matter is related
> to digital TV (#linuxtv) and another one for the rest (#v4l), both
> at freenode.
>
> That's something that wouldn't fit well into MAINTAINERS file, as
> we can't explain what should be used for each.
>
> So, the way it is it won't work well for us.
So maybe add a comment to both like:
C: <URI1> # only for digital tv #linuxtv
C: <URI2> # everything else
next prev parent reply other threads:[~2018-11-26 17:13 UTC|newest]
Thread overview: 173+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 4:53 [Ksummit-discuss] [RFC PATCH 0/3] Maintainer Handbook: Subsystem Profile Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 4:53 ` [Ksummit-discuss] [RFC PATCH 1/3] MAINTAINERS: Reclaim the P: tag for " Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 5:39 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2018-11-15 5:39 ` Mauro Carvalho Chehab
2018-11-15 5:39 ` Mauro Carvalho Chehab
2018-11-15 20:12 ` Joe Perches
2018-11-15 20:12 ` Joe Perches
2018-11-15 20:12 ` Joe Perches
2018-11-15 4:53 ` [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: " Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 5:48 ` [Ksummit-discuss] " Julia Lawall
2018-11-15 5:48 ` Julia Lawall
2018-11-15 5:48 ` Julia Lawall
2018-11-15 7:59 ` Geert Uytterhoeven
2018-11-15 7:59 ` Geert Uytterhoeven
2018-11-15 7:59 ` Geert Uytterhoeven
2018-11-15 13:47 ` Julia Lawall
2018-11-15 13:47 ` Julia Lawall
2018-11-15 13:47 ` Julia Lawall
2018-11-16 12:44 ` Jani Nikula
2018-11-16 12:44 ` Jani Nikula
2018-11-16 12:44 ` Jani Nikula
2018-11-16 17:56 ` Joe Perches
2018-11-16 17:56 ` Joe Perches
2018-11-16 17:56 ` Joe Perches
2018-11-17 14:12 ` Rob Herring
2018-11-17 14:12 ` Rob Herring
2018-11-17 14:12 ` Rob Herring
2018-11-17 17:03 ` Julia Lawall
2018-11-17 17:03 ` Julia Lawall
2018-11-17 17:03 ` Julia Lawall
2018-11-20 7:28 ` Jani Nikula
2018-11-20 7:28 ` Jani Nikula
2018-11-20 7:28 ` Jani Nikula
2018-11-15 5:49 ` Mauro Carvalho Chehab
2018-11-15 5:49 ` Mauro Carvalho Chehab
2018-11-15 5:49 ` Mauro Carvalho Chehab
2018-11-15 7:58 ` Geert Uytterhoeven
2018-11-15 7:58 ` Geert Uytterhoeven
2018-11-15 7:58 ` Geert Uytterhoeven
2018-11-15 8:38 ` Jani Nikula
2018-11-15 8:38 ` Jani Nikula
2018-11-15 8:38 ` Jani Nikula
2018-11-15 18:03 ` Tim.Bird
2018-11-15 18:03 ` Tim.Bird
2018-11-15 18:03 ` Tim.Bird
2018-11-15 23:56 ` Tobin C. Harding
2018-11-15 23:56 ` Tobin C. Harding
2018-11-15 23:56 ` Tobin C. Harding
2018-11-15 15:44 ` Mauro Carvalho Chehab
2018-11-15 15:44 ` Mauro Carvalho Chehab
2018-11-15 15:44 ` Mauro Carvalho Chehab
2018-11-16 23:28 ` Randy Dunlap
2018-11-16 23:28 ` Randy Dunlap
2018-11-16 23:28 ` Randy Dunlap
2018-11-17 11:57 ` Hans Verkuil
2018-11-17 11:57 ` Hans Verkuil
2018-11-17 11:57 ` Hans Verkuil
2018-11-16 0:11 ` Frank Rowand
2018-11-16 0:11 ` Frank Rowand
2018-11-16 0:11 ` Frank Rowand
2018-11-16 12:04 ` Mauro Carvalho Chehab
2018-11-16 12:04 ` Mauro Carvalho Chehab
2018-11-16 12:04 ` Mauro Carvalho Chehab
2018-11-16 18:57 ` Dan Williams
2018-11-16 18:57 ` Dan Williams
2018-11-16 18:57 ` Dan Williams
2018-11-18 12:58 ` Mauro Carvalho Chehab
2018-11-18 12:58 ` Mauro Carvalho Chehab
2018-11-18 12:58 ` Mauro Carvalho Chehab
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:31 ` Dan Williams
2018-11-18 17:34 ` Dan Williams
2018-11-18 17:34 ` Dan Williams
2018-11-18 17:34 ` Dan Williams
2018-11-18 17:44 ` Mauro Carvalho Chehab
2018-11-18 17:44 ` Mauro Carvalho Chehab
2018-11-18 17:44 ` Mauro Carvalho Chehab
2018-11-16 16:47 ` Frank Rowand
2018-11-16 16:47 ` Frank Rowand
2018-11-16 16:47 ` Frank Rowand
2018-11-15 4:53 ` [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: " Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 4:53 ` Dan Williams
2018-11-15 8:03 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-15 8:03 ` Geert Uytterhoeven
2018-11-15 8:03 ` Geert Uytterhoeven
2018-11-15 14:10 ` Mauro Carvalho Chehab
2018-11-15 14:10 ` Mauro Carvalho Chehab
2018-11-15 14:10 ` Mauro Carvalho Chehab
2018-11-15 16:20 ` Leon Romanovsky
2018-11-15 16:20 ` Leon Romanovsky
2018-11-15 19:09 ` Mauro Carvalho Chehab
2018-11-15 19:09 ` Mauro Carvalho Chehab
2018-11-15 19:35 ` Leon Romanovsky
2018-11-15 19:35 ` Leon Romanovsky
2018-11-15 19:40 ` Luck, Tony
2018-11-15 19:40 ` Luck, Tony
2018-11-15 19:40 ` Luck, Tony
2018-11-15 19:43 ` Joe Perches
2018-11-15 19:43 ` Joe Perches
2018-11-15 19:43 ` Joe Perches
2018-11-16 11:39 ` Mauro Carvalho Chehab
2018-11-16 11:39 ` Mauro Carvalho Chehab
2018-11-16 11:39 ` Mauro Carvalho Chehab
2018-11-18 7:12 ` Leon Romanovsky
2018-11-18 7:12 ` Leon Romanovsky
2018-11-18 7:12 ` Leon Romanovsky
2018-11-16 11:33 ` Mauro Carvalho Chehab
2018-11-16 11:33 ` Mauro Carvalho Chehab
2018-11-16 12:00 ` Jan Kara
2018-11-16 12:00 ` Jan Kara
2018-11-16 12:00 ` Jan Kara
2018-11-18 7:00 ` Leon Romanovsky
2018-11-16 20:36 ` Rodrigo Vivi
2018-11-16 20:36 ` Rodrigo Vivi
2018-11-16 20:36 ` Rodrigo Vivi
2018-11-16 23:44 ` Dan Williams
2018-11-16 23:44 ` Dan Williams
2018-11-16 23:44 ` Dan Williams
2018-11-17 0:38 ` NeilBrown
2018-11-17 0:38 ` NeilBrown
2018-11-18 13:11 ` Mauro Carvalho Chehab
2018-11-18 13:11 ` Mauro Carvalho Chehab
2018-11-18 13:11 ` Mauro Carvalho Chehab
2018-11-18 13:03 ` Mauro Carvalho Chehab
2018-11-18 13:03 ` Mauro Carvalho Chehab
2018-11-18 13:03 ` Mauro Carvalho Chehab
2018-11-20 8:10 ` Jani Nikula
2018-11-20 8:10 ` Jani Nikula
2018-11-20 19:31 ` Dan Williams
2018-11-20 19:31 ` Dan Williams
2018-11-20 19:31 ` Dan Williams
2018-11-26 11:12 ` Mauro Carvalho Chehab
2018-11-26 11:12 ` Mauro Carvalho Chehab
2018-11-26 11:12 ` Mauro Carvalho Chehab
2018-11-26 15:55 ` Joe Perches [this message]
2018-11-26 15:55 ` Joe Perches
2018-11-26 15:55 ` Joe Perches
2018-11-16 19:13 ` Dan Williams
2018-11-16 19:13 ` Dan Williams
2018-11-16 19:13 ` Dan Williams
2018-11-15 14:30 ` Mauro Carvalho Chehab
2018-11-15 14:30 ` Mauro Carvalho Chehab
2018-11-15 14:30 ` Mauro Carvalho Chehab
2018-11-15 14:51 ` Julia Lawall
2018-11-15 14:51 ` Julia Lawall
2018-11-15 14:51 ` Julia Lawall
2018-11-16 19:20 ` Dan Williams
2018-11-16 19:20 ` Dan Williams
2018-11-16 19:20 ` Dan Williams
2018-11-16 2:58 ` y-goto
2018-11-16 2:58 ` y-goto
2018-11-16 2:58 ` y-goto
2018-11-17 0:32 ` [Ksummit-discuss] " David Woodhouse
2018-11-17 0:32 ` David Woodhouse
2018-11-15 5:56 ` [Ksummit-discuss] [RFC PATCH 0/3] Maintainer Handbook: " Mauro Carvalho Chehab
2018-11-15 5:56 ` Mauro Carvalho Chehab
2018-11-15 5:56 ` Mauro Carvalho Chehab
2018-11-25 10:57 ` [Ksummit-discuss] " Pavel Machek
2018-11-25 10:57 ` Pavel Machek
2018-11-25 20:55 ` [Ksummit-discuss] " Dan Williams
2018-11-25 20:55 ` Dan Williams
2018-11-25 20:55 ` Dan Williams
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=52ff06c49ec35599b3c8edf3bd3d1acbb9397c91.camel@perches.com \
--to=joe@perches.com \
--cc=jani.nikula@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mchehab+samsung@kernel.org \
--cc=zwisler@kernel.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.