From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: Zap lpc32xx_ssp driver-related code
Date: Sat, 27 Apr 2019 22:08:34 +0200 [thread overview]
Message-ID: <7dab08c9-bb14-4917-d446-c3b6304760b9@gmail.com> (raw)
In-Reply-To: <20190422210024.GT4664@bill-the-cat>
On 22.04.19 23:00, Tom Rini wrote:
> On Mon, Apr 22, 2019 at 11:50:22PM +0300, Vladimir Zapolskiy wrote:
>> Hi Jagan, Tom,
>>
>> On 04/19/2019 09:48 AM, Jagan Teki wrote:
>>> Dropped
>>> - lpc32xx_ssp driver
>>> - CONFIG_LPC32XX_SSP, LPC32XX_SSP_TIMEOUT items
>>>
>>> Dropped due to:
>>> - no active updates
>>> - no dm conversion
>>> - multiple pings for asking dm-conversion
>>
>> I really don't want to rush into moaning, however let me ask you to drop
>> the reason given above as invalid, otherwise please clarify who were
>> the addressees of these 'multiple pings'.
>
> Indeed. Since it was only last month or so that I setup a low-traffic
> list for maintainers / custodians for important issues like this, [..]
Wait, which list are you talking about? Should I be monitoring anything
else than this one?
Regards,
Simon
next prev parent reply other threads:[~2019-04-27 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 6:48 [U-Boot] [PATCH] spi: Zap lpc32xx_ssp driver-related code Jagan Teki
2019-04-21 18:43 ` Tom Rini
2019-04-24 7:41 ` Jagan Teki
2019-04-24 11:47 ` Tom Rini
2019-04-22 20:50 ` Vladimir Zapolskiy
2019-04-22 21:00 ` Tom Rini
2019-04-27 20:08 ` Simon Goldschmidt [this message]
2019-04-29 0:22 ` Tom Rini
2019-04-29 8:22 ` Simon Goldschmidt
2019-04-29 17:57 ` Tom Rini
2019-04-29 18:09 ` Simon Goldschmidt
2019-04-24 6:44 ` Jagan Teki
2019-04-24 11:48 ` Tom Rini
2019-04-25 18:13 ` Jagan Teki
2019-04-25 18:17 ` Tom Rini
2019-04-25 18:20 ` 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=7dab08c9-bb14-4917-d446-c3b6304760b9@gmail.com \
--to=simon.k.r.goldschmidt@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox