From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/8] sf: improve support of (Q)SPI flash memories
Date: Fri, 25 Aug 2017 18:45:20 +0200 [thread overview]
Message-ID: <53a2419c-a85c-82ba-a4ee-059b2e6a1626@denx.de> (raw)
In-Reply-To: <CAD6G_RSHq6E_+157zseOhYAhvsHKHCzfLw4tcbHzB7vQAs11Mg@mail.gmail.com>
On 08/25/2017 06:28 PM, Jagan Teki wrote:
> On Fri, Aug 25, 2017 at 9:43 PM, Marek Vasut <marex@denx.de> wrote:
>> On 08/25/2017 06:07 PM, Jagan Teki wrote:
>>> On Fri, Aug 25, 2017 at 6:47 AM, Yang, Wenyou <Wenyou.Yang@microchip.com> wrote:
>>>> Hi,
>>>>
>>>> This patch set has been here for a long time, could you have a look and take
>>>> it?
>>>
>>> Yeah, I'm holding this because of my current spi-nor work. But anyway
>>> I will try to merge on coming MW If all OK.
>>
>> Is your work posted somewhere or available in some git repository ?
You did not answer this question.
>> I don't see any reason why you should not perform your maintainer duties
>> by reviewing/replying to an incoming patch, no matter what work you do
>> to the subsystem though ...
>
> I didn't write "this series holding spi-nor work" since it has some
> new features I'm taking time to review.
I never implied this. Rather the opposite, you claim you do some work on
the SPI NOR core, yet you let this patchset rot in the list for over a
month now and gave the author zero feedback.
Notifying the author about the core changes early could've prevented a
lot of wasted effort on his side. Reviewing early could've prevented a
lot of frustration from patches being ignored.
> There is nothing wrong with
> maintainer duties here, you must need to understand.
I disagree.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-08-25 16:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 7:00 [U-Boot] [PATCH v3 0/8] sf: improve support of (Q)SPI flash memories Wenyou Yang
2017-07-25 7:00 ` [U-Boot] [PATCH v3 1/8] spi: add support of SPI flash commands Wenyou Yang
2017-08-30 13:50 ` Jagan Teki
2017-09-01 0:10 ` Wenyou.Yang at microchip.com
2017-07-25 7:00 ` [U-Boot] [PATCH v3 2/8] sf: describe all SPI flash commands with 'struct spi_flash_command' Wenyou Yang
2017-08-30 14:03 ` Jagan Teki
2017-07-25 7:00 ` [U-Boot] [PATCH v3 3/8] sf: select the relevant SPI flash protocol for read and write commands Wenyou Yang
2017-07-25 7:00 ` [U-Boot] [PATCH v3 4/8] sf: differentiate Page Program 1-1-4 and 1-4-4 Wenyou Yang
2017-07-25 7:00 ` [U-Boot] [PATCH v3 5/8] sf: add 'addr_len' member to 'struct spi_flash' Wenyou Yang
2017-07-25 7:01 ` [U-Boot] [PATCH v3 6/8] sf: add new option to support SPI flash above 16MiB Wenyou Yang
2017-07-25 7:01 ` [U-Boot] [PATCH v3 7/8] sf: add support to Microchip SST26 QSPI memories Wenyou Yang
2017-07-25 7:01 ` [U-Boot] [PATCH v3 8/8] sf: add driver for Atmel QSPI controller Wenyou Yang
2017-08-30 13:58 ` Jagan Teki
2017-07-31 7:29 ` [U-Boot] [PATCH v3 0/8] sf: improve support of (Q)SPI flash memories Yang, Wenyou
2017-08-11 1:02 ` Yang, Wenyou
2017-08-11 5:14 ` Jagan Teki
2017-08-25 1:17 ` Yang, Wenyou
2017-08-25 16:07 ` Jagan Teki
2017-08-25 16:13 ` Marek Vasut
2017-08-25 16:28 ` Jagan Teki
2017-08-25 16:45 ` Marek Vasut [this message]
2017-08-25 23:05 ` Bin Meng
2017-08-26 6:14 ` Jagan Teki
2017-08-26 8:36 ` Marek Vasut
2017-08-26 19:12 ` Tom Rini
2017-08-26 6:34 ` Jagan Teki
2017-08-30 1:58 ` Yang, Wenyou
2017-08-30 6:33 ` Jagan Teki
2017-08-30 3:25 ` Yang, Wenyou
2017-08-30 3:43 ` Bin Meng
2017-08-30 5:27 ` Yang, Wenyou
2017-08-30 5:41 ` Bin Meng
2017-08-30 5:51 ` Yang, Wenyou
2017-08-30 6:30 ` Jagan Teki
2017-08-30 7:47 ` Bin Meng
2017-08-30 13:25 ` Jagan Teki
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=53a2419c-a85c-82ba-a4ee-059b2e6a1626@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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.