All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "William Zhang" <william.zhang@broadcom.com>,
	"Linux MTD List" <linux-mtd@lists.infradead.org>,
	"Linux ARM List" <linux-arm-kernel@lists.infradead.org>,
	"Broadcom Kernel List" <bcm-kernel-feedback-list@broadcom.com>,
	f.fainelli@gmail.com, kursad.oney@broadcom.com,
	joel.peshkin@broadcom.com, anand.gore@broadcom.com,
	dregan@mail.com, kamal.dasu@broadcom.com,
	tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Kamal Dasu" <kdasu.kdev@gmail.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"David Regan" <dregan@broadcom.com>,
	devicetree@vger.kernel.org,
	"Alexandre TORGUE" <alexandre.torgue@st.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Brian Norris" <computersforpeace@gmail.com>,
	"Shawn Guo" <shawnguo@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Richard Weinberger" <richard@nod.at>
Subject: Re: [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates
Date: Thu, 14 Mar 2024 23:04:02 +0100	[thread overview]
Message-ID: <20240314230402.5fc7bbf3@xps-13> (raw)
In-Reply-To: <20240229101101.5208195c@xps-13>

Hi Florian,

miquel.raynal@bootlin.com wrote on Thu, 29 Feb 2024 10:11:01 +0100:

> Hi Florian,
> 
> florian.fainelli@broadcom.com wrote on Mon, 26 Feb 2024 09:36:02 -0800:
> 
> > On 2/22/24 19:47, William Zhang wrote:  
> > > This patch series is an update from the previous version [1] after
> > > exex_op support and fixes (patch 1 to 4 from the previous version.)
> > > 
> > > It updates all the BCMBCA SoC to support the nand controller and add
> > > functions to handle BCMBCA specific needs on ECC and Write Protection
> > > usage. The device tree document is also updated accordingly with the new
> > > properties needed by the driver.
> > > 
> > > In addition there is a bug fix for exec_op helper functions, log level
> > > adjustment on uncorrectable ECC error and some coding style fixes.
> > > 
> > > [1] https://lore.kernel.org/lkml/20230606231252.94838-1-william.zhang@broadcom.com/    
> > 
> > Miquel, thanks for having applied the patches, we should have discussed ahead of time whether you should take the SoC/board-level DTS changes through your tree or mine, but it's fine either way and should not lead to conflicts in Linus' tree.  
> 
> I'm sorry for not thinking about this ahead of time, I was also not
> Cced on the other patches, I noticed it (told Willliam) and just forgot
> about this when I applied the series.
> 
> It is currently living in -next so if there is any problem I can still
> act.
> 
> However for this kind of change I usually apply the bindings and .c
> changes independently from the DT patches. I believe there is no
> problem having one or the other being merged first, or do I overlook
> something?

What the heck /o\ I just understand now my mistake, I am very truly
sorry for that...

You were telling me I should sync with you before taking DT changes,
and I was so convinced I _did_not_ take the DT, when I looked at the
branch I did not understand your point. But I am totally sorry I
actually did take the DTs by mistake and I truly did not notice it.
Confirmation bias I suppose. My very sincere apologies.

As mentioned previously, I was not CC'ed on the DT patches, but I
believe the linux-mtd list was, so the patches didn't appear in my
inbox, and once I was happy with the binding/driver changes I applied
it all without noticing the DT changes had sneaked in.

I'm finally preparing the PR for Linus and I see it now...

I believe the SoC tree is closed now so it's up to you what I should do
with them. Let me know if you want me to keep them in my tree and
forward them to Linus or if I should drop them and you'll take them for
the next cycle. Also, if I keep them, shall I add some tag of yours on
these 3 patches? For the record I did not review them.

Thanks and again, I'm confused. I never apply DT patches like that,
your initial remark was more than legitimate.

Cheers,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "William Zhang" <william.zhang@broadcom.com>,
	"Linux MTD List" <linux-mtd@lists.infradead.org>,
	"Linux ARM List" <linux-arm-kernel@lists.infradead.org>,
	"Broadcom Kernel List" <bcm-kernel-feedback-list@broadcom.com>,
	f.fainelli@gmail.com, kursad.oney@broadcom.com,
	joel.peshkin@broadcom.com, anand.gore@broadcom.com,
	dregan@mail.com, kamal.dasu@broadcom.com,
	tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Kamal Dasu" <kdasu.kdev@gmail.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"David Regan" <dregan@broadcom.com>,
	devicetree@vger.kernel.org,
	"Alexandre TORGUE" <alexandre.torgue@st.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Brian Norris" <computersforpeace@gmail.com>,
	"Shawn Guo" <shawnguo@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Richard Weinberger" <richard@nod.at>
Subject: Re: [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates
Date: Thu, 14 Mar 2024 23:04:02 +0100	[thread overview]
Message-ID: <20240314230402.5fc7bbf3@xps-13> (raw)
In-Reply-To: <20240229101101.5208195c@xps-13>

Hi Florian,

miquel.raynal@bootlin.com wrote on Thu, 29 Feb 2024 10:11:01 +0100:

> Hi Florian,
> 
> florian.fainelli@broadcom.com wrote on Mon, 26 Feb 2024 09:36:02 -0800:
> 
> > On 2/22/24 19:47, William Zhang wrote:  
> > > This patch series is an update from the previous version [1] after
> > > exex_op support and fixes (patch 1 to 4 from the previous version.)
> > > 
> > > It updates all the BCMBCA SoC to support the nand controller and add
> > > functions to handle BCMBCA specific needs on ECC and Write Protection
> > > usage. The device tree document is also updated accordingly with the new
> > > properties needed by the driver.
> > > 
> > > In addition there is a bug fix for exec_op helper functions, log level
> > > adjustment on uncorrectable ECC error and some coding style fixes.
> > > 
> > > [1] https://lore.kernel.org/lkml/20230606231252.94838-1-william.zhang@broadcom.com/    
> > 
> > Miquel, thanks for having applied the patches, we should have discussed ahead of time whether you should take the SoC/board-level DTS changes through your tree or mine, but it's fine either way and should not lead to conflicts in Linus' tree.  
> 
> I'm sorry for not thinking about this ahead of time, I was also not
> Cced on the other patches, I noticed it (told Willliam) and just forgot
> about this when I applied the series.
> 
> It is currently living in -next so if there is any problem I can still
> act.
> 
> However for this kind of change I usually apply the bindings and .c
> changes independently from the DT patches. I believe there is no
> problem having one or the other being merged first, or do I overlook
> something?

What the heck /o\ I just understand now my mistake, I am very truly
sorry for that...

You were telling me I should sync with you before taking DT changes,
and I was so convinced I _did_not_ take the DT, when I looked at the
branch I did not understand your point. But I am totally sorry I
actually did take the DTs by mistake and I truly did not notice it.
Confirmation bias I suppose. My very sincere apologies.

As mentioned previously, I was not CC'ed on the DT patches, but I
believe the linux-mtd list was, so the patches didn't appear in my
inbox, and once I was happy with the binding/driver changes I applied
it all without noticing the DT changes had sneaked in.

I'm finally preparing the PR for Linus and I see it now...

I believe the SoC tree is closed now so it's up to you what I should do
with them. Let me know if you want me to keep them in my tree and
forward them to Linus or if I should drop them and you'll take them for
the next cycle. Also, if I keep them, shall I add some tag of yours on
these 3 patches? For the record I did not review them.

Thanks and again, I'm confused. I never apply DT patches like that,
your initial remark was more than legitimate.

Cheers,
Miquèl

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "William Zhang" <william.zhang@broadcom.com>,
	"Linux MTD List" <linux-mtd@lists.infradead.org>,
	"Linux ARM List" <linux-arm-kernel@lists.infradead.org>,
	"Broadcom Kernel List" <bcm-kernel-feedback-list@broadcom.com>,
	f.fainelli@gmail.com, kursad.oney@broadcom.com,
	joel.peshkin@broadcom.com, anand.gore@broadcom.com,
	dregan@mail.com, kamal.dasu@broadcom.com,
	tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Kamal Dasu" <kdasu.kdev@gmail.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"David Regan" <dregan@broadcom.com>,
	devicetree@vger.kernel.org,
	"Alexandre TORGUE" <alexandre.torgue@st.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Brian Norris" <computersforpeace@gmail.com>,
	"Shawn Guo" <shawnguo@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Richard Weinberger" <richard@nod.at>
Subject: Re: [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates
Date: Thu, 14 Mar 2024 23:04:02 +0100	[thread overview]
Message-ID: <20240314230402.5fc7bbf3@xps-13> (raw)
In-Reply-To: <20240229101101.5208195c@xps-13>

Hi Florian,

miquel.raynal@bootlin.com wrote on Thu, 29 Feb 2024 10:11:01 +0100:

> Hi Florian,
> 
> florian.fainelli@broadcom.com wrote on Mon, 26 Feb 2024 09:36:02 -0800:
> 
> > On 2/22/24 19:47, William Zhang wrote:  
> > > This patch series is an update from the previous version [1] after
> > > exex_op support and fixes (patch 1 to 4 from the previous version.)
> > > 
> > > It updates all the BCMBCA SoC to support the nand controller and add
> > > functions to handle BCMBCA specific needs on ECC and Write Protection
> > > usage. The device tree document is also updated accordingly with the new
> > > properties needed by the driver.
> > > 
> > > In addition there is a bug fix for exec_op helper functions, log level
> > > adjustment on uncorrectable ECC error and some coding style fixes.
> > > 
> > > [1] https://lore.kernel.org/lkml/20230606231252.94838-1-william.zhang@broadcom.com/    
> > 
> > Miquel, thanks for having applied the patches, we should have discussed ahead of time whether you should take the SoC/board-level DTS changes through your tree or mine, but it's fine either way and should not lead to conflicts in Linus' tree.  
> 
> I'm sorry for not thinking about this ahead of time, I was also not
> Cced on the other patches, I noticed it (told Willliam) and just forgot
> about this when I applied the series.
> 
> It is currently living in -next so if there is any problem I can still
> act.
> 
> However for this kind of change I usually apply the bindings and .c
> changes independently from the DT patches. I believe there is no
> problem having one or the other being merged first, or do I overlook
> something?

What the heck /o\ I just understand now my mistake, I am very truly
sorry for that...

You were telling me I should sync with you before taking DT changes,
and I was so convinced I _did_not_ take the DT, when I looked at the
branch I did not understand your point. But I am totally sorry I
actually did take the DTs by mistake and I truly did not notice it.
Confirmation bias I suppose. My very sincere apologies.

As mentioned previously, I was not CC'ed on the DT patches, but I
believe the linux-mtd list was, so the patches didn't appear in my
inbox, and once I was happy with the binding/driver changes I applied
it all without noticing the DT changes had sneaked in.

I'm finally preparing the PR for Linus and I see it now...

I believe the SoC tree is closed now so it's up to you what I should do
with them. Let me know if you want me to keep them in my tree and
forward them to Linus or if I should drop them and you'll take them for
the next cycle. Also, if I keep them, shall I add some tag of yours on
these 3 patches? For the record I did not review them.

Thanks and again, I'm confused. I never apply DT patches like that,
your initial remark was more than legitimate.

Cheers,
Miquèl

  parent reply	other threads:[~2024-03-14 22:04 UTC|newest]

Thread overview: 120+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  3:47 [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates William Zhang
2024-02-23  3:47 ` William Zhang
2024-02-23  3:47 ` William Zhang
2024-02-23  3:47 ` [PATCH v6 01/13] mtd: rawnand: brcmnand: exec_op helper functions return type fixes William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  4:20   ` Florian Fainelli
2024-02-23  4:20     ` Florian Fainelli
2024-02-23  4:20     ` Florian Fainelli
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 02/13] mtd: rawnand: brcmnand: fix style issues William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 03/13] mtd: rawnand: brcmnand: update log level messages William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 04/13] dt-bindings: mtd: brcmnand: Updates for bcmbca SoCs William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 05/13] dt-bindings: mtd: brcmnand: Add WP pin connection property William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 06/13] dt-bindings: mtd: brcmnand: Add ecc strap property William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23 18:47   ` Conor Dooley
2024-02-23 18:47     ` Conor Dooley
2024-02-23 18:47     ` Conor Dooley
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 07/13] ARM: dts: broadcom: bcmbca: Add NAND controller node William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 08/13] arm64: " William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 09/13] arm64: dts: broadcom: bcmbca: Update router boards William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:44   ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-26 10:44     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 10/13] mtd: rawnand: brcmnand: Rename bcm63138 nand driver William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:43   ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 11/13] mtd: rawnand: brcmnand: Add BCMBCA read data bus interface William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:43   ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-23  3:47 ` [PATCH v6 12/13] mtd: rawnand: brcmnand: Add support for getting ecc setting from strap William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  9:18   ` Miquel Raynal
2024-02-23  9:18     ` Miquel Raynal
2024-02-23  9:18     ` Miquel Raynal
2024-02-23 17:25     ` William Zhang
2024-02-23 17:25       ` William Zhang
2024-02-23 17:25       ` William Zhang
2024-02-26  8:36       ` Miquel Raynal
2024-02-26  8:36         ` Miquel Raynal
2024-02-26  8:36         ` Miquel Raynal
2024-02-26 20:05         ` William Zhang
2024-02-26 20:05           ` William Zhang
2024-02-26 20:05           ` William Zhang
2024-02-29 10:31           ` Miquel Raynal
2024-02-29 10:31             ` Miquel Raynal
2024-02-29 10:31             ` Miquel Raynal
2024-02-29 23:34             ` William Zhang
2024-02-29 23:34               ` William Zhang
2024-02-29 23:34               ` William Zhang
2024-02-23  3:47 ` [PATCH v6 13/13] mtd: rawnand: brcmnand: Support write protection setting from dts William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-23  3:47   ` William Zhang
2024-02-26 10:43   ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-26 10:43     ` Miquel Raynal
2024-02-26 17:36 ` [PATCH v6 00/13] mtd: rawnand: brcmnand: driver and doc updates Florian Fainelli
2024-02-26 17:36   ` Florian Fainelli
2024-02-26 17:36   ` Florian Fainelli
2024-02-29  9:11   ` Miquel Raynal
2024-02-29  9:11     ` Miquel Raynal
2024-02-29  9:11     ` Miquel Raynal
2024-02-29 17:32     ` Florian Fainelli
2024-02-29 17:32       ` Florian Fainelli
2024-02-29 17:32       ` Florian Fainelli
2024-03-14 22:04     ` Miquel Raynal [this message]
2024-03-14 22:04       ` Miquel Raynal
2024-03-14 22:04       ` Miquel Raynal
2024-03-14 23:02       ` Florian Fainelli
2024-03-14 23:02         ` Florian Fainelli
2024-03-14 23:02         ` Florian Fainelli
2024-03-14 23:03         ` Miquel Raynal
2024-03-14 23:03           ` Miquel Raynal
2024-03-14 23:03           ` Miquel Raynal

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=20240314230402.5fc7bbf3@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexandre.torgue@st.com \
    --cc=anand.gore@broadcom.com \
    --cc=andre.przywara@arm.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=dan.beygelman@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dregan@broadcom.com \
    --cc=dregan@mail.com \
    --cc=f.fainelli@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=kamal.dasu@broadcom.com \
    --cc=kdasu.kdev@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=tomer.yacoby@broadcom.com \
    --cc=vigneshr@ti.com \
    --cc=william.zhang@broadcom.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.