From: kraxel@redhat.com (Gerd Hoffmann)
Subject: [PATCH v6] Add udmabuf misc device
Date: Wed, 4 Jul 2018 10:58:25 +0200 [thread overview]
Message-ID: <20180704085825.nfkv5i7ultaavjve@sirius.home.kraxel.org> (raw)
Message-ID: <20180704085825.iOYb_9u5RE-HHLlVE05SukRHq6aP8V2394U2n5S4XDY@z> (raw)
In-Reply-To: <20180704080807.GH3891@phenom.ffwll.local>
Hi,
> > Hmm, does MAINTAINERS need an update then? Maintainer and mailing lists
> > listed in the "DMA BUFFER SHARING FRAMEWORK" entry are on Cc.
>
> Yeah, maintainers entry with you as maintainer plus dri-devel as mailing
> list plus drm-misc as repo would be good. Just grep for drm-misc.git for
> tons of examples.
There is an *existing* entry covering drivers/dma-buf/, and I've dropped
udmabuf.c into that directory, so I've assumed get_maintainers.pl picks
up all relevant dma-buf folks ...
Covering udmabuf.c maintainance is a different issue. I could just add
myself to the existing entry, or create a new one specifically for
udmabuf.
> > Who should be Cc'ed?
>
> dim add-missing-cc ftw :-)
That just uses get_maintainer.pl according to the docs, so that wouldn't
change things as that is wired up as sendemail.cccmd already. Except
that dim would probably add the list of people to the commit message.
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-04 8:58 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 7:53 [PATCH v6] Add udmabuf misc device Gerd Hoffmann
2018-07-03 7:53 ` Gerd Hoffmann
2018-07-03 7:53 ` Gerd Hoffmann
2018-07-03 7:53 ` kraxel
2018-07-03 7:53 ` Gerd Hoffmann
2018-07-03 8:37 ` Daniel Vetter
2018-07-03 8:37 ` Daniel Vetter
2018-07-03 8:37 ` Daniel Vetter
2018-07-03 8:37 ` daniel
2018-07-03 8:37 ` Daniel Vetter
2018-07-03 8:37 ` Daniel Vetter
2018-07-04 5:53 ` Gerd Hoffmann
2018-07-04 5:53 ` Gerd Hoffmann
2018-07-04 5:53 ` Gerd Hoffmann
2018-07-04 5:53 ` kraxel
2018-07-04 5:53 ` Gerd Hoffmann
2018-07-04 5:53 ` Gerd Hoffmann
2018-07-04 7:26 ` Tomeu Vizoso
2018-07-04 7:26 ` Tomeu Vizoso
2018-07-04 7:26 ` Tomeu Vizoso
2018-07-04 7:26 ` tomeu.vizoso
2018-07-04 7:26 ` Tomeu Vizoso
2018-07-04 7:26 ` Tomeu Vizoso
2018-07-04 8:00 ` Gerd Hoffmann
2018-07-04 8:00 ` Gerd Hoffmann
2018-07-04 8:00 ` Gerd Hoffmann
2018-07-04 8:00 ` kraxel
2018-07-04 8:00 ` Gerd Hoffmann
2018-07-04 8:00 ` Gerd Hoffmann
2018-07-06 4:00 ` Dave Airlie
2018-07-06 4:00 ` Dave Airlie
2018-07-06 4:00 ` Dave Airlie
2018-07-06 4:00 ` airlied
2018-07-06 4:00 ` Dave Airlie
2018-07-06 4:00 ` Dave Airlie
2018-08-30 15:17 ` Tomeu Vizoso
2018-08-30 15:17 ` Tomeu Vizoso
2018-08-30 15:17 ` tomeu.vizoso
2018-08-30 15:17 ` Tomeu Vizoso
2018-08-31 7:04 ` Gerd Hoffmann
2018-08-31 7:04 ` Gerd Hoffmann
2018-08-31 7:04 ` Gerd Hoffmann
2018-08-31 7:04 ` kraxel
2018-08-31 7:04 ` Gerd Hoffmann
2018-07-04 8:08 ` Daniel Vetter
2018-07-04 8:08 ` Daniel Vetter
2018-07-04 8:08 ` Daniel Vetter
2018-07-04 8:08 ` daniel
2018-07-04 8:08 ` Daniel Vetter
2018-07-04 8:08 ` Daniel Vetter
2018-07-04 8:58 ` Gerd Hoffmann [this message]
2018-07-04 8:58 ` Gerd Hoffmann
2018-07-04 8:58 ` Gerd Hoffmann
2018-07-04 8:58 ` kraxel
2018-07-04 8:58 ` Gerd Hoffmann
2018-07-04 8:58 ` Gerd Hoffmann
2018-07-04 9:19 ` Daniel Vetter
2018-07-04 9:19 ` Daniel Vetter
2018-07-04 9:19 ` Daniel Vetter
2018-07-04 9:19 ` daniel
2018-07-04 9:19 ` Daniel Vetter
2018-07-04 9:19 ` Daniel Vetter
2018-08-27 9:34 ` Gerd Hoffmann
2018-08-27 9:34 ` Gerd Hoffmann
2018-08-27 9:34 ` kraxel
2018-08-27 9:34 ` Gerd Hoffmann
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=20180704085825.nfkv5i7ultaavjve@sirius.home.kraxel.org \
--to=kraxel@redhat.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 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.