From: Jonathan Cameron <jic23@kernel.org>
To: Brian Masney <masneyb@onstation.org>, linux-iio@vger.kernel.org
Subject: Re: Question about submitting patch set against staging/iio/light/tsl2583
Date: Sun, 30 Oct 2016 12:51:54 +0000 [thread overview]
Message-ID: <391f639d-2784-7b9d-46c2-a3570aee33e8@kernel.org> (raw)
In-Reply-To: <20161026173825.GA21767@basecamp.onstation.org>
On 26/10/16 18:38, Brian Masney wrote:
> Part of the tsl2583 driver cleanup that I am working on involves adding
> device tree support to that driver. Based on the isl29018 driver cleanups
> that I did, I now know that the device tree maintainers should be CCed for
> any device tree changes. What is the appropriate way to submit my patch
> set that spans two different subsystems? Should I submit my lone device
> tree patch to linux-iio and CC the device tree maintainers? Then submit
> the rest of my patch set to just the linux-iio maintainers? Or should I
> CC the device tree maintainers with my entire patch set? I'm leaning
> towards the separate approach to reduce the amount of noise to the
> device tree list.
Kind of depends on the balance of device tree to other elements in the series.
Either way create a whole series with all changes, but then add a Cc: line to the
patch description for the device tree ones. git send-email will then pick that
up and add CCs for those patches only as it sends them.
Sometimes it's easier just to CC the whole lot. Kernel reviewers get very
good at rapidly ignoring patch emails that aren't of interest to them!
J
>
> Brian
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-10-30 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:38 Question about submitting patch set against staging/iio/light/tsl2583 Brian Masney
2016-10-30 12:51 ` Jonathan Cameron [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=391f639d-2784-7b9d-46c2-a3570aee33e8@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=masneyb@onstation.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).