On Fri, Jan 22, 2016 at 11:30:55AM -0600, Han Xu wrote: > On Fri, Jan 22, 2016 at 3:01 AM, Yao Yuan <yao.y...@nxp.com> wrote: > > On Thu, Jan 21, 2016 at 11:42 PM, Han Xu < xhnj...@gmail.com > wrote: > >> On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.y...@freescale.com> wrote: > >> > Any extra information you can find them on the patchwork: > >> > https://patchwork.kernel.org/patch/8078931/ > >> > https://patchwork.kernel.org/patch/8078951/ > >> > https://patchwork.kernel.org/patch/8079091/ > >> > https://patchwork.kernel.org/patch/8078941/ > >> > >> Please send all patches in one patch set, this is not acceptable. > >> > > > > Thanks for your review. > > But those patches are dts binding patch. And will send to > > devicet...@vger.kernel.org and some corresponding maintainer. > > > > Those two patch sets will send to different mail-list and maintainers > > separately. > > > > So, maybe it's better to send the patch to the maintainer accordingly and > > thus I think can also reduce the workload of maintainer. > > > > How about your think? > > Send the complete patch set to maintainer and cc all related > sub-module groups, so everybody could understand the whole story.
Agreed. You apparently did not read the suggested documentation from last time: Documentation/devicetree/bindings/submitting-patches.txt Particularly, points 2 and 3. Subsystem maintainers merge binding patches, so please send them as part of the regular series. Brian
