From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: <broonie@kernel.org>, <devicetree@vger.kernel.org>,
<vigneshr@ti.com>, <richard@nod.at>,
<linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<robh+dt@kernel.org>, <linux-mediatek@lists.infradead.org>,
<miquel.raynal@bootlin.com>, <matthias.bgg@gmail.com>,
<gch981213@gmail.com>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 09:11:29 +0000 [thread overview]
Message-ID: <4427171.IzkiAjLLdB@localhost.localdomain> (raw)
In-Reply-To: <2471214.x7VzW1FXlQ@localhost.localdomain>
On Tuesday, March 10, 2020 9:41:26 AM EET Tudor.Ambarus@microchip.com wrote:
> Hi, Mark,
>
> On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > > This driver is superseded by the new spi-mtk-nor driver.
> > >
> > > Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> >
> > Is this move OK from a MTD point of view - should I apply this when the
> > rest goes in? The patch was in prior versions too and is obviously
> > straightforward.
>
> If you find the rest of the patches ok, this can go through the spi tree,
> feel free to add my
> Acked-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> There will be a conflict with the following patch https://
> patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
You can also create an immutable tag that I can merge in my spi-nor/next
branch, so that Linus doesn't have to deal with the conflict.
ta
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
To: <linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Cc: <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<vigneshr-l0cyMroinI0@public.gmane.org>,
<richard-/L3Ra7n9ekc@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
<linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
<miquel.raynal-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>,
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
<gch981213-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 09:11:29 +0000 [thread overview]
Message-ID: <4427171.IzkiAjLLdB@localhost.localdomain> (raw)
In-Reply-To: <2471214.x7VzW1FXlQ-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Tuesday, March 10, 2020 9:41:26 AM EET Tudor.Ambarus-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org wrote:
> Hi, Mark,
>
> On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > > This driver is superseded by the new spi-mtk-nor driver.
> > >
> > > Signed-off-by: Chuanhong Guo <gch981213-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >
> > Is this move OK from a MTD point of view - should I apply this when the
> > rest goes in? The patch was in prior versions too and is obviously
> > straightforward.
>
> If you find the rest of the patches ok, this can go through the spi tree,
> feel free to add my
> Acked-by: Tudor Ambarus <tudor.ambarus-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
>
> There will be a conflict with the following patch https://
> patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
You can also create an immutable tag that I can merge in my spi-nor/next
branch, so that Linus doesn't have to deal with the conflict.
ta
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: devicetree@vger.kernel.org, vigneshr@ti.com, richard@nod.at,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, broonie@kernel.org,
linux-mediatek@lists.infradead.org, miquel.raynal@bootlin.com,
matthias.bgg@gmail.com, gch981213@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 09:11:29 +0000 [thread overview]
Message-ID: <4427171.IzkiAjLLdB@localhost.localdomain> (raw)
In-Reply-To: <2471214.x7VzW1FXlQ@localhost.localdomain>
On Tuesday, March 10, 2020 9:41:26 AM EET Tudor.Ambarus@microchip.com wrote:
> Hi, Mark,
>
> On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > > This driver is superseded by the new spi-mtk-nor driver.
> > >
> > > Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> >
> > Is this move OK from a MTD point of view - should I apply this when the
> > rest goes in? The patch was in prior versions too and is obviously
> > straightforward.
>
> If you find the rest of the patches ok, this can go through the spi tree,
> feel free to add my
> Acked-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> There will be a conflict with the following patch https://
> patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
You can also create an immutable tag that I can merge in my spi-nor/next
branch, so that Linus doesn't have to deal with the conflict.
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: devicetree@vger.kernel.org, vigneshr@ti.com, richard@nod.at,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, broonie@kernel.org,
linux-mediatek@lists.infradead.org, miquel.raynal@bootlin.com,
matthias.bgg@gmail.com, gch981213@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 09:11:29 +0000 [thread overview]
Message-ID: <4427171.IzkiAjLLdB@localhost.localdomain> (raw)
In-Reply-To: <2471214.x7VzW1FXlQ@localhost.localdomain>
On Tuesday, March 10, 2020 9:41:26 AM EET Tudor.Ambarus@microchip.com wrote:
> Hi, Mark,
>
> On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > > This driver is superseded by the new spi-mtk-nor driver.
> > >
> > > Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> >
> > Is this move OK from a MTD point of view - should I apply this when the
> > rest goes in? The patch was in prior versions too and is obviously
> > straightforward.
>
> If you find the rest of the patches ok, this can go through the spi tree,
> feel free to add my
> Acked-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> There will be a conflict with the following patch https://
> patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
You can also create an immutable tag that I can merge in my spi-nor/next
branch, so that Linus doesn't have to deal with the conflict.
ta
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <linux-mtd@lists.infradead.org>
Cc: devicetree@vger.kernel.org, vigneshr@ti.com, richard@nod.at,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, broonie@kernel.org,
linux-mediatek@lists.infradead.org, miquel.raynal@bootlin.com,
matthias.bgg@gmail.com, gch981213@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver
Date: Tue, 10 Mar 2020 09:11:29 +0000 [thread overview]
Message-ID: <4427171.IzkiAjLLdB@localhost.localdomain> (raw)
In-Reply-To: <2471214.x7VzW1FXlQ@localhost.localdomain>
On Tuesday, March 10, 2020 9:41:26 AM EET Tudor.Ambarus@microchip.com wrote:
> Hi, Mark,
>
> On Monday, March 9, 2020 2:10:20 PM EET Mark Brown wrote:
> > > This driver is superseded by the new spi-mtk-nor driver.
> > >
> > > Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> >
> > Is this move OK from a MTD point of view - should I apply this when the
> > rest goes in? The patch was in prior versions too and is obviously
> > straightforward.
>
> If you find the rest of the patches ok, this can go through the spi tree,
> feel free to add my
> Acked-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>
> There will be a conflict with the following patch https://
> patchwork.ozlabs.org/patch/1247791/, but nothing that we can't handle.
You can also create an immutable tag that I can merge in my spi-nor/next
branch, so that Linus doesn't have to deal with the conflict.
ta
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-10 9:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 8:50 [PATCH v3 0/4] rewrite mtk-quadspi spi-nor driver with spi-mem Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 1/4] spi: make spi-max-frequency optional Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 2/4] spi: add support for mediatek spi-nor controller Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` [PATCH v3 3/4] dt-bindings: convert mtk-quadspi binding doc for spi-mtk-nor Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-11 18:35 ` Applied "dt-bindings: convert mtk-quadspi binding doc for spi-mtk-nor" to the spi tree Mark Brown
2020-03-11 18:35 ` Mark Brown
2020-03-11 18:35 ` Mark Brown
2020-03-11 18:35 ` Mark Brown
2020-03-11 18:35 ` Mark Brown
2020-03-06 8:50 ` [PATCH v3 4/4] mtd: spi-nor: remove mtk-quadspi driver Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-06 8:50 ` Chuanhong Guo
2020-03-09 12:10 ` Mark Brown
2020-03-09 12:10 ` Mark Brown
2020-03-09 12:10 ` Mark Brown
2020-03-09 12:10 ` Mark Brown
2020-03-09 12:10 ` Mark Brown
2020-03-10 7:41 ` Tudor.Ambarus
2020-03-10 7:41 ` Tudor.Ambarus
2020-03-10 7:41 ` Tudor.Ambarus
2020-03-10 7:41 ` Tudor.Ambarus
2020-03-10 9:11 ` Tudor.Ambarus [this message]
2020-03-10 9:11 ` Tudor.Ambarus
2020-03-10 9:11 ` Tudor.Ambarus
2020-03-10 9:11 ` Tudor.Ambarus
2020-03-10 9:11 ` Tudor.Ambarus-UWL1GkI3JZL3oGB3hsPCZA
2020-03-11 19:57 ` Mark Brown
2020-03-11 19:57 ` Mark Brown
2020-03-11 19:57 ` Mark Brown
2020-03-11 19:57 ` Mark Brown
2020-03-11 19:57 ` Mark Brown
2020-03-11 19:00 ` Patchwork summary for: spi-devel-general patchwork-bot+linux-spi-DgEjT+Ai2ygdnm+yROfE0A
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=4427171.IzkiAjLLdB@localhost.localdomain \
--to=tudor.ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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: link
Be 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.