From: <Tudor.Ambarus@microchip.com>
To: <masonccyang@mxic.com.tw>, <broonie@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>,
<marek.vasut@gmail.com>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <vigneshr@ti.com>,
<bbrezillon@kernel.org>
Cc: <juliensu@mxic.com.tw>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH 0/4] mtd: spi-nor: Add support for Octal 8D-8D-8D mode
Date: Tue, 10 Dec 2019 17:00:45 +0000 [thread overview]
Message-ID: <8f2908ec-6e17-dad1-7f2a-ec22647caecb@microchip.com> (raw)
In-Reply-To: <1573808288-19365-1-git-send-email-masonccyang@mxic.com.tw>
Hi, Mason,
From the discussion you had with Vignesh, I understand that a v2 will follow. A
nit below.
On 11/15/19 10:58 AM, Mason Yang wrote:
> Hello,
>
> This is repost of patchset from Boris Brezillon's
> [RFC,00/18] mtd: spi-nor: Proposal for 8-8-8 mode support [1].
>
[cut]
> Mason Yang (4):
Did you intentionally overwrite Boris's authorship? If yes, would you please
describe what changed from Boris's patch set?
Cheers,
ta
WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <masonccyang@mxic.com.tw>, <broonie@kernel.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>,
<marek.vasut@gmail.com>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <vigneshr@ti.com>,
<bbrezillon@kernel.org>
Cc: juliensu@mxic.com.tw, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 0/4] mtd: spi-nor: Add support for Octal 8D-8D-8D mode
Date: Tue, 10 Dec 2019 17:00:45 +0000 [thread overview]
Message-ID: <8f2908ec-6e17-dad1-7f2a-ec22647caecb@microchip.com> (raw)
In-Reply-To: <1573808288-19365-1-git-send-email-masonccyang@mxic.com.tw>
Hi, Mason,
From the discussion you had with Vignesh, I understand that a v2 will follow. A
nit below.
On 11/15/19 10:58 AM, Mason Yang wrote:
> Hello,
>
> This is repost of patchset from Boris Brezillon's
> [RFC,00/18] mtd: spi-nor: Proposal for 8-8-8 mode support [1].
>
[cut]
> Mason Yang (4):
Did you intentionally overwrite Boris's authorship? If yes, would you please
describe what changed from Boris's patch set?
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-12-10 17:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 8:58 [PATCH 0/4] mtd: spi-nor: Add support for Octal 8D-8D-8D mode Mason Yang
2019-11-15 8:58 ` Mason Yang
2019-11-15 8:58 ` [PATCH 1/4] spi: spi-mem: " Mason Yang
2019-11-15 8:58 ` Mason Yang
2019-11-15 8:58 ` [PATCH 2/4] mtd: spi-nor: " Mason Yang
2019-11-15 8:58 ` Mason Yang
2019-11-15 12:30 ` kbuild test robot
2019-11-15 12:30 ` kbuild test robot
2019-11-15 12:30 ` kbuild test robot
2019-11-15 13:42 ` kbuild test robot
2019-11-15 13:42 ` kbuild test robot
2019-11-15 13:42 ` kbuild test robot
2019-12-04 12:46 ` Vignesh Raghavendra
2019-12-04 12:46 ` Vignesh Raghavendra
2019-12-09 7:56 ` masonccyang
2019-12-09 7:56 ` masonccyang
2019-12-09 9:53 ` Vignesh Raghavendra
2019-12-09 9:53 ` Vignesh Raghavendra
2019-12-10 7:21 ` masonccyang
2019-12-10 7:21 ` masonccyang
2019-11-15 8:58 ` [PATCH 3/4] mtd: spi-nor: Add Octal 8D-8D-8D mode support for Macronix mx25uw51245g Mason Yang
2019-11-15 8:58 ` Mason Yang
2019-12-04 13:03 ` Vignesh Raghavendra
2019-12-04 13:03 ` Vignesh Raghavendra
2019-12-09 6:38 ` masonccyang
2019-12-09 6:38 ` masonccyang
2019-11-15 8:58 ` [PATCH 4/4] spi: mxic: Add support for Octal 8D-8D-8D mode Mason Yang
2019-11-15 8:58 ` Mason Yang
2019-11-15 14:39 ` kbuild test robot
2019-11-15 14:39 ` kbuild test robot
2019-11-15 14:39 ` kbuild test robot
2019-11-16 7:20 ` kbuild test robot
2019-11-16 7:20 ` kbuild test robot
2019-11-16 7:20 ` kbuild test robot
2019-12-10 17:00 ` Tudor.Ambarus [this message]
2019-12-10 17:00 ` [PATCH 0/4] mtd: spi-nor: " Tudor.Ambarus
2019-12-11 2:14 ` masonccyang
2019-12-11 2:14 ` masonccyang
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=8f2908ec-6e17-dad1-7f2a-ec22647caecb@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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.