From: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Incomplete information in MAINTAINERS
Date: Sat, 01 Mar 2014 09:41:31 +0100 [thread overview]
Message-ID: <53119D3B.3050406@gmx.de> (raw)
In-Reply-To: <CAL_JsqK9Wquv6kgefyPvy0JqXNO7Cx2+iN_ss=CtgXnKEjrF-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello Rob,
you wrote
>> Also, there is a newly created list for dtc specific topics:
>> http://vger.kernel.org/vger-lists.html#devicetree-compiler
Could you, please, have file MAINTAINERS updated to include
aforementioned list. Otherwise scripts/get_maintainer.pl
will not show it.
Best regards
Heinrich Schuchardt
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-01 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:24 [PATCH 1/1] Memory leak in scripts/dtc/util.c xypron.glpk-Mmb7MZpHnFY
2014-02-27 18:24 ` xypron.glpk
2014-02-28 1:32 ` Rob Herring
[not found] ` <CAL_JsqK9Wquv6kgefyPvy0JqXNO7Cx2+iN_ss=CtgXnKEjrF-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-01 8:11 ` [PATCH 1/1] Remove dead code in util.c xypron.glpk-Mmb7MZpHnFY
2014-03-01 8:11 ` xypron.glpk
[not found] ` <1393661507-7197-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-03-02 13:11 ` David Gibson
2014-03-02 13:11 ` David Gibson
2014-03-01 8:41 ` Heinrich Schuchardt [this message]
[not found] ` <53119D3B.3050406-Mmb7MZpHnFY@public.gmane.org>
2014-03-03 13:26 ` Incomplete information in MAINTAINERS Rob Herring
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=53119D3B.3050406@gmx.de \
--to=xypron.glpk-mmb7mzphnfy@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@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.