All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ramuthevar, Vadivel MuruganX"  <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Anders Roxell <anders.roxell@linaro.org>,
	Andriy Shevchenko <andriy.shevchenko@intel.com>,
	Brendan Higgins <brendanhiggins@google.com>,
	cheol.yong.kim@intel.com, devicetree <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:MEMORY TECHNOLOGY..." <linux-mtd@lists.infradead.org>,
	masonccyang@mxic.com.tw,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Piotr Sroka <piotrs@cadence.com>,
	qi-ming.wu@intel.com, Richard Weinberger <richard@nod.at>,
	Rob Herring <robh+dt@kernel.org>, Vignesh R <vigneshr@ti.com>,
	Songjun Wu <songjun.wu@linux.intel.com>,
	yixin.zhu@linux.intel.com, chuanhua.lei@linux.intel.com,
	John Crispin <john@phrozen.org>
Subject: Re: [PATCH v1 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC
Date: Mon, 20 Apr 2020 09:09:01 +0800	[thread overview]
Message-ID: <fababbbf-c520-3c03-356a-77846076151f@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a1rYDfTW60eY3RiiSOeT9EsNxw2rxMuQ9UjaS+JDiHy3Q@mail.gmail.com>

Hi Arnd,

On 16/4/2020 9:20 pm, Arnd Bergmann wrote:
> On Thu, Apr 16, 2020 at 2:40 PM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
>> On Thu, 16 Apr 2020 15:26:51 +0300
>> Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>>> On Thu, Apr 16, 2020 at 3:03 PM Boris Brezillon
>>> <boris.brezillon@collabora.com> wrote:
>>>> On Thu, 16 Apr 2020 19:38:03 +0800
>>>> Note that the NAND subsystem is full of unmaintained legacy drivers, so
>>>> every time we see someone who could help us get rid or update one of
>>>> them we have to take this opportunity.
>>> Don't we rather insist to have a MAINTAINERS record for new code to
>>> avoid (or delay at least) the fate of the legacy drivers?
>>>
>> Well, that's what we do for new drivers, but the xway driver has been
>> added in 2012 and the policy was not enforced at that time. BTW, that
>> goes for most of the legacy drivers in have in the NAND subsystems
>> (some of them even predate the git era).
>>
>> To be clear, I just checked and there's no official maintainer for this
>> driver. Best option would be to Cc the original author and contributors
>> who proposed functional changes to the code, as well as the MIPS
>> maintainers (Xway is a MIPS platform).
> A lot of the pre-acquisition code for lantiq was contributed by Hauke
> Mehrtens and John Crispin. There was an intermediate generation of
> MIPS SoCs with patches posted for review  by Intel in 2018 (presumably
> by the same organizatiob), but those were never resubmitted after v2
> and never merged:
>
> https://lore.kernel.org/linux-mips/20180803030237.3366-1-songjun.wu@linux.intel.com/
Thank you for reviewing our patches and your time...
The above patches for different SoC which is MIPS based, but whatever 
the patch is sent by me is Intel X86 ATOM based LGM SoC.

Regards
Vadivel
>
>          Arnd

WARNING: multiple messages have this Message-ID (diff)
From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: cheol.yong.kim@intel.com, devicetree <devicetree@vger.kernel.org>,
	qi-ming.wu@intel.com, Anders Roxell <anders.roxell@linaro.org>,
	Andriy Shevchenko <andriy.shevchenko@intel.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Richard Weinberger <richard@nod.at>,
	John Crispin <john@phrozen.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	yixin.zhu@linux.intel.com, Vignesh R <vigneshr@ti.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	"open list:MEMORY TECHNOLOGY..." <linux-mtd@lists.infradead.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	chuanhua.lei@linux.intel.com, masonccyang@mxic.com.tw,
	Songjun Wu <songjun.wu@linux.intel.com>,
	Piotr Sroka <piotrs@cadence.com>
Subject: Re: [PATCH v1 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC
Date: Mon, 20 Apr 2020 09:09:01 +0800	[thread overview]
Message-ID: <fababbbf-c520-3c03-356a-77846076151f@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a1rYDfTW60eY3RiiSOeT9EsNxw2rxMuQ9UjaS+JDiHy3Q@mail.gmail.com>

Hi Arnd,

On 16/4/2020 9:20 pm, Arnd Bergmann wrote:
> On Thu, Apr 16, 2020 at 2:40 PM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
>> On Thu, 16 Apr 2020 15:26:51 +0300
>> Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>>> On Thu, Apr 16, 2020 at 3:03 PM Boris Brezillon
>>> <boris.brezillon@collabora.com> wrote:
>>>> On Thu, 16 Apr 2020 19:38:03 +0800
>>>> Note that the NAND subsystem is full of unmaintained legacy drivers, so
>>>> every time we see someone who could help us get rid or update one of
>>>> them we have to take this opportunity.
>>> Don't we rather insist to have a MAINTAINERS record for new code to
>>> avoid (or delay at least) the fate of the legacy drivers?
>>>
>> Well, that's what we do for new drivers, but the xway driver has been
>> added in 2012 and the policy was not enforced at that time. BTW, that
>> goes for most of the legacy drivers in have in the NAND subsystems
>> (some of them even predate the git era).
>>
>> To be clear, I just checked and there's no official maintainer for this
>> driver. Best option would be to Cc the original author and contributors
>> who proposed functional changes to the code, as well as the MIPS
>> maintainers (Xway is a MIPS platform).
> A lot of the pre-acquisition code for lantiq was contributed by Hauke
> Mehrtens and John Crispin. There was an intermediate generation of
> MIPS SoCs with patches posted for review  by Intel in 2018 (presumably
> by the same organizatiob), but those were never resubmitted after v2
> and never merged:
>
> https://lore.kernel.org/linux-mips/20180803030237.3366-1-songjun.wu@linux.intel.com/
Thank you for reviewing our patches and your time...
The above patches for different SoC which is MIPS based, but whatever 
the patch is sent by me is Intel X86 ATOM based LGM SoC.

Regards
Vadivel
>
>          Arnd

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

  parent reply	other threads:[~2020-04-20  1:09 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  2:24 [PATCH v1 0/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-14  2:24 ` Ramuthevar, Vadivel MuruganX
2020-04-14  2:24 ` [PATCH v1 1/2] dt-bindings: mtd: Add YAML for Nand Flash Controller support Ramuthevar,Vadivel MuruganX
2020-04-14  2:24   ` Ramuthevar, Vadivel MuruganX
2020-04-14  7:04   ` Boris Brezillon
2020-04-14  7:04     ` Boris Brezillon
2020-04-15  1:51     ` Ramuthevar, Vadivel MuruganX
2020-04-15  1:51       ` Ramuthevar, Vadivel MuruganX
2020-04-14  2:24 ` [PATCH v1 2/2] mtd: rawnand: Add NAND controller support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-04-14  2:24   ` Ramuthevar, Vadivel MuruganX
2020-04-14  7:21   ` Boris Brezillon
2020-04-14  7:21     ` Boris Brezillon
2020-04-15  6:01     ` Ramuthevar, Vadivel MuruganX
2020-04-15  6:01       ` Ramuthevar, Vadivel MuruganX
2020-04-15 22:05   ` Martin Blumenstingl
2020-04-15 22:05     ` Martin Blumenstingl
2020-04-16  9:35     ` Ramuthevar, Vadivel MuruganX
2020-04-16  9:35       ` Ramuthevar, Vadivel MuruganX
2020-04-16  9:38       ` Boris Brezillon
2020-04-16  9:38         ` Boris Brezillon
2020-04-16  9:45         ` Ramuthevar, Vadivel MuruganX
2020-04-16  9:45           ` Ramuthevar, Vadivel MuruganX
2020-04-16 10:26           ` Boris Brezillon
2020-04-16 10:26             ` Boris Brezillon
2020-04-16 10:40             ` Ramuthevar, Vadivel MuruganX
2020-04-16 10:40               ` Ramuthevar, Vadivel MuruganX
2020-04-16 11:17               ` Boris Brezillon
2020-04-16 11:17                 ` Boris Brezillon
2020-04-16 11:32                 ` Andy Shevchenko
2020-04-16 11:32                   ` Andy Shevchenko
2020-04-17  5:10                   ` Ramuthevar, Vadivel MuruganX
2020-04-17  5:10                     ` Ramuthevar, Vadivel MuruganX
     [not found]                 ` <de9f50b8-9215-d294-9914-e49701552185@linux.intel.com>
2020-04-16 11:57                   ` Boris Brezillon
2020-04-16 11:57                     ` Boris Brezillon
2020-04-16 12:26                     ` Andy Shevchenko
2020-04-16 12:26                       ` Andy Shevchenko
2020-04-16 12:40                       ` Boris Brezillon
2020-04-16 12:40                         ` Boris Brezillon
2020-04-16 13:20                         ` Arnd Bergmann
2020-04-16 13:20                           ` Arnd Bergmann
2020-04-16 13:51                           ` John Crispin
2020-04-16 13:51                             ` John Crispin
2020-04-20  1:09                           ` Ramuthevar, Vadivel MuruganX [this message]
2020-04-20  1:09                             ` Ramuthevar, Vadivel MuruganX
2020-04-16 18:08                     ` Martin Blumenstingl
2020-04-16 18:08                       ` Martin Blumenstingl
2020-04-17  5:21                     ` Ramuthevar, Vadivel MuruganX
2020-04-17  5:21                       ` Ramuthevar, Vadivel MuruganX
2020-04-17  7:02                       ` Boris Brezillon
2020-04-17  7:02                         ` Boris Brezillon
2020-04-17  7:53                         ` Ramuthevar, Vadivel MuruganX
2020-04-17  7:53                           ` 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=fababbbf-c520-3c03-356a-77846076151f@linux.intel.com \
    --to=vadivel.muruganx.ramuthevar@linux.intel.com \
    --cc=anders.roxell@linaro.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=boris.brezillon@collabora.com \
    --cc=brendanhiggins@google.com \
    --cc=cheol.yong.kim@intel.com \
    --cc=chuanhua.lei@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=masonccyang@mxic.com.tw \
    --cc=miquel.raynal@bootlin.com \
    --cc=piotrs@cadence.com \
    --cc=qi-ming.wu@intel.com \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=songjun.wu@linux.intel.com \
    --cc=vigneshr@ti.com \
    --cc=yixin.zhu@linux.intel.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.