From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com> To: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org>, Vignesh R <vigneshr@ti.com>, Mark Rutland <mark.rutland@arm.com>, Rob Herring <robh+dt@kernel.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@vger.kernel.org>, dan.carpenter@oracle.com, cheol.yong.kim@intel.com, qi-ming.wu@intel.com Subject: Re: [PATCH v9 0/2] spi: cadence-quadpsi: Add support for the Cadence QSPI controller Date: Mon, 17 Feb 2020 18:11:14 +0800 [thread overview] Message-ID: <48e60c06-62d5-4965-97d1-51577da3bbcf@linux.intel.com> (raw) In-Reply-To: <CAAh8qsxnRSwonuEPrriuS=gUMTjt8ddUVy5HxegmoCk-FoE4qg@mail.gmail.com> Hi Simon, On 14/2/2020 8:02 PM, Simon Goldschmidt wrote: > On Fri, Feb 14, 2020 at 12:46 PM Ramuthevar,Vadivel MuruganX > <vadivel.muruganx.ramuthevar@linux.intel.com> wrote: >> Add support for the Cadence QSPI controller. This controller is >> present in the Intel Lightning Mountain(LGM) SoCs, Altera and TI SoCs. >> This driver has been tested on the Intel LGM SoCs. > This is v9 and still, none of the altera maintainers are on CC? > How will it be ensured that this doesn't break altera if it is merged? Thanks for reminded me, sorry, next send time will add them in CC. Regards Vadivel > > Regards, > Simon >
WARNING: multiple messages have this Message-ID (diff)
From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> To: Simon Goldschmidt <simon.k.r.goldschmidt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Vignesh R <vigneshr-l0cyMroinI0@public.gmane.org>, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org, cheol.yong.kim-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, qi-ming.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Subject: Re: [PATCH v9 0/2] spi: cadence-quadpsi: Add support for the Cadence QSPI controller Date: Mon, 17 Feb 2020 18:11:14 +0800 [thread overview] Message-ID: <48e60c06-62d5-4965-97d1-51577da3bbcf@linux.intel.com> (raw) In-Reply-To: <CAAh8qsxnRSwonuEPrriuS=gUMTjt8ddUVy5HxegmoCk-FoE4qg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Hi Simon, On 14/2/2020 8:02 PM, Simon Goldschmidt wrote: > On Fri, Feb 14, 2020 at 12:46 PM Ramuthevar,Vadivel MuruganX > <vadivel.muruganx.ramuthevar-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> wrote: >> Add support for the Cadence QSPI controller. This controller is >> present in the Intel Lightning Mountain(LGM) SoCs, Altera and TI SoCs. >> This driver has been tested on the Intel LGM SoCs. > This is v9 and still, none of the altera maintainers are on CC? > How will it be ensured that this doesn't break altera if it is merged? Thanks for reminded me, sorry, next send time will add them in CC. Regards Vadivel > > Regards, > Simon >
next prev parent reply other threads:[~2020-02-17 10:11 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-14 11:46 [PATCH v9 0/2] spi: cadence-quadpsi: Add support for the Cadence QSPI controller Ramuthevar,Vadivel MuruganX 2020-02-14 11:46 ` Ramuthevar,Vadivel MuruganX 2020-02-14 11:46 ` [PATCH v9 1/2] dt-bindings: spi: Add schema for Cadence QSPI Controller driver Ramuthevar,Vadivel MuruganX 2020-02-14 11:46 ` Ramuthevar,Vadivel MuruganX 2020-02-14 14:08 ` Mark Brown 2020-02-14 14:08 ` Mark Brown 2020-02-14 11:46 ` [PATCH v9 2/2] spi: cadence-quadpsi: Add support for the Cadence QSPI controller Ramuthevar,Vadivel MuruganX 2020-02-14 11:46 ` Ramuthevar,Vadivel MuruganX 2020-02-14 13:09 ` Mark Brown 2020-02-14 13:09 ` Mark Brown 2020-02-17 9:18 ` Ramuthevar, Vadivel MuruganX 2020-02-17 9:18 ` Ramuthevar, Vadivel MuruganX 2020-02-17 17:09 ` Mark Brown 2020-02-17 17:09 ` Mark Brown 2020-02-18 3:17 ` Ramuthevar, Vadivel MuruganX 2020-02-18 3:17 ` Ramuthevar, Vadivel MuruganX 2020-02-14 12:02 ` [PATCH v9 0/2] " Simon Goldschmidt 2020-02-14 12:02 ` Simon Goldschmidt 2020-02-14 12:11 ` Mark Brown 2020-02-14 12:11 ` Mark Brown 2020-02-14 12:50 ` Simon Goldschmidt 2020-02-14 12:50 ` Simon Goldschmidt 2020-02-14 13:15 ` Mark Brown 2020-02-14 13:15 ` Mark Brown 2020-02-14 13:49 ` Simon Goldschmidt 2020-02-14 13:49 ` Simon Goldschmidt 2020-02-14 14:16 ` Mark Brown 2020-02-14 14:16 ` Mark Brown 2020-02-17 10:09 ` Ramuthevar, Vadivel MuruganX 2020-02-17 10:09 ` Ramuthevar, Vadivel MuruganX [not found] ` <4712cdc4-34cd-990b-3d53-3d394ae1250b@linux.intel.com> 2020-02-17 11:52 ` Mark Brown 2020-02-17 11:52 ` Mark Brown 2020-02-17 12:18 ` Vignesh Raghavendra 2020-02-17 12:18 ` Vignesh Raghavendra 2020-02-18 8:56 ` Ramuthevar, Vadivel MuruganX 2020-02-18 8:56 ` Ramuthevar, Vadivel MuruganX 2020-02-17 10:11 ` Ramuthevar, Vadivel MuruganX [this message] 2020-02-17 10:11 ` Ramuthevar, Vadivel MuruganX
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=48e60c06-62d5-4965-97d1-51577da3bbcf@linux.intel.com \ --to=vadivel.muruganx.ramuthevar@linux.intel.com \ --cc=broonie@kernel.org \ --cc=cheol.yong.kim@intel.com \ --cc=dan.carpenter@oracle.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=qi-ming.wu@intel.com \ --cc=robh+dt@kernel.org \ --cc=simon.k.r.goldschmidt@gmail.com \ --cc=vigneshr@ti.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.