linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Question about submitting patch set against staging/iio/light/tsl2583
@ 2016-10-26 17:38 Brian Masney
  2016-10-30 12:51 ` Jonathan Cameron
  0 siblings, 1 reply; 2+ messages in thread
From: Brian Masney @ 2016-10-26 17:38 UTC (permalink / raw)
  To: linux-iio

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.

Brian


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Question about submitting patch set against staging/iio/light/tsl2583
  2016-10-26 17:38 Question about submitting patch set against staging/iio/light/tsl2583 Brian Masney
@ 2016-10-30 12:51 ` Jonathan Cameron
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Cameron @ 2016-10-30 12:51 UTC (permalink / raw)
  To: Brian Masney, linux-iio

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
> 


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-10-30 12:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).