Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1314282 > unrolled thread

Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a

Started byHan Xu <xhnjupt@gmail.com>
First post2016-01-21 16:50 +0100
Last post2016-01-24 06:00 +0100
Articles 5 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a Han Xu <xhnjupt@gmail.com> - 2016-01-21 16:50 +0100
    RE: mtd: spi-nor: fsl-quadspi: add support for ls1021a Yao Yuan <yao.yuan@nxp.com> - 2016-01-22 10:10 +0100
      Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a Han Xu <xhnjupt@gmail.com> - 2016-01-22 18:40 +0100
        Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a Brian Norris <computersforpeace@gmail.com> - 2016-01-23 22:20 +0100
          Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a Yao Yuan <yao.yuan@nxp.com> - 2016-01-24 06:00 +0100

#1314282 — Re: mtd: spi-nor: fsl-quadspi: add support for ls1021a

FromHan Xu <xhnjupt@gmail.com>
Date2016-01-21 16:50 +0100
SubjectRe: mtd: spi-nor: fsl-quadspi: add support for ls1021a
Message-ID<qTpEK-7eF-13@gated-at.bofh.it>
On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.yuan@freescale.com> wrote:
> This patch set is used for add the fsl-quadspi support for ls1021a and
> ls1043a, so remove the patch:
> mtd: spi-nor: fsl-quadspi: extend support for some special requerment.

Please use --cover-letter to generate cover letter.

>
> This patch will be send with anther patch set for add QSPI support on LS2080A.
>
> All the new property are document in anther patch set which is already
> send to linux-kernel@vger.kernel.org and devicetree@vger.kernel.org.
> Here is the patch name:
> 0001-Documentation-fsl-quadspi-Add-fsl-ls2080a-dspi-compa.patch
> 0002-Documentation-fsl-quadspi-Add-fsl-ls2080a-qspi-compa.patch
> 0003-dts-ls2080a-update-the-DTS-for-QSPI-and-DSPI-support.patch
> 0004-Documentation-fsl-quadspi-Add-optional-properties.patch
>
> 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.
>
> Yuan Yao.
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

[toc] | [next] | [standalone]


#1314839

FromYao Yuan <yao.yuan@nxp.com>
Date2016-01-22 10:10 +0100
Message-ID<qTFTd-1Xj-29@gated-at.bofh.it>
In reply to#1314282
On Thu, Jan 21, 2016 at 11:42 PM, Han Xu < xhnjupt@gmail.com > wrote:
> On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.yuan@freescale.com> wrote:
> > This patch set is used for add the fsl-quadspi support for ls1021a and
> > ls1043a, so remove the patch:
> > mtd: spi-nor: fsl-quadspi: extend support for some special requerment.
> 
> Please use --cover-letter to generate cover letter.
> 
> >
> > This patch will be send with anther patch set for add QSPI support on LS2080A.
> >
> > All the new property are document in anther patch set which is already
> > send to linux-kernel@vger.kernel.org and devicetree@vger.kernel.org.
> > Here is the patch name:
> > 0001-Documentation-fsl-quadspi-Add-fsl-ls2080a-dspi-compa.patch
> > 0002-Documentation-fsl-quadspi-Add-fsl-ls2080a-qspi-compa.patch
> > 0003-dts-ls2080a-update-the-DTS-for-QSPI-and-DSPI-support.patch
> > 0004-Documentation-fsl-quadspi-Add-optional-properties.patch
> >
> > 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  devicetree@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?

Thanks.

Yuan Yao.

[toc] | [prev] | [next] | [standalone]


#1315165

FromHan Xu <xhnjupt@gmail.com>
Date2016-01-22 18:40 +0100
Message-ID<qTNQK-7gK-15@gated-at.bofh.it>
In reply to#1314839
On Fri, Jan 22, 2016 at 3:01 AM, Yao Yuan <yao.yuan@nxp.com> wrote:
> On Thu, Jan 21, 2016 at 11:42 PM, Han Xu < xhnjupt@gmail.com > wrote:
>> On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.yuan@freescale.com> wrote:
>> > This patch set is used for add the fsl-quadspi support for ls1021a and
>> > ls1043a, so remove the patch:
>> > mtd: spi-nor: fsl-quadspi: extend support for some special requerment.
>>
>> Please use --cover-letter to generate cover letter.
>>
>> >
>> > This patch will be send with anther patch set for add QSPI support on LS2080A.
>> >
>> > All the new property are document in anther patch set which is already
>> > send to linux-kernel@vger.kernel.org and devicetree@vger.kernel.org.
>> > Here is the patch name:
>> > 0001-Documentation-fsl-quadspi-Add-fsl-ls2080a-dspi-compa.patch
>> > 0002-Documentation-fsl-quadspi-Add-fsl-ls2080a-qspi-compa.patch
>> > 0003-dts-ls2080a-update-the-DTS-for-QSPI-and-DSPI-support.patch
>> > 0004-Documentation-fsl-quadspi-Add-optional-properties.patch
>> >
>> > 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  devicetree@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.

> Thanks.
>
> Yuan Yao.

[toc] | [prev] | [next] | [standalone]


#1315758

FromBrian Norris <computersforpeace@gmail.com>
Date2016-01-23 22:20 +0100
Message-ID<qUdLc-1BD-5@gated-at.bofh.it>
In reply to#1315165
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.yuan@nxp.com> wrote:
> > On Thu, Jan 21, 2016 at 11:42 PM, Han Xu < xhnjupt@gmail.com > wrote:
> >> On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.yuan@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  devicetree@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

[toc] | [prev] | [next] | [standalone]


#1315823

FromYao Yuan <yao.yuan@nxp.com>
Date2016-01-24 06:00 +0100
Message-ID<qUkWl-81Y-1@gated-at.bofh.it>
In reply to#1315758
On Sun, Jan 24, 2016 05:17 AM +0800, Brian Norris wrote:
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.yuan@nxp.com> wrote:
> > On Thu, Jan 21, 2016 at 11:42 PM, Han Xu < xhnjupt@gmail.com > wrote:
> >> On Thu, Jan 21, 2016 at 1:53 AM, Yuan Yao <yao.yuan@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  devicetree@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.

OK, Got it.
Thanks Han Xu and  Brian Norris.

I will resend them as a complete patch set.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web