linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: IIO: clarification about posting patches with device tree elements.
Date: Mon, 16 Sep 2013 20:25:48 +0100	[thread overview]
Message-ID: <52375B3C.8020203@kernel.org> (raw)

Hi All,

As I was unclear on when we needed Acks from the device tree maintainers
I posted an enquiry to devietree@vger.kernel.org.  Rob Herring kindly
replied. http://www.spinics.net/lists/devicetree/msg04669.html


In brief:

1) All device tree bindings related patches should be cc'd to
devicetree@vger.kernel.org

2) Anything new (i.e. not the same as in existing drivers)
   needs an Ack from a device tree maintainer.

3) Any changes to common bindings needs an Ack from a device tree
   maintainer.

4) Anything else 'interesting' may need an Ack.

Anyhow, please all remember to cc devicetree@vger.kernel.org for
anything DT related.

Thanks,

Jonathan

                 reply	other threads:[~2013-09-16 18:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52375B3C.8020203@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).