U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 29 Apr 2019 20:09:57 +0200	[thread overview]
Message-ID: <5d53ee82-ffb3-a280-5a40-caadfddf92f6@gmail.com> (raw)
In-Reply-To: <20190429175755.GZ31207@bill-the-cat>

Am 29.04.2019 um 19:57 schrieb Tom Rini:
> On Mon, Apr 29, 2019 at 10:22:07AM +0200, Simon Goldschmidt wrote:
>> On Mon, Apr 29, 2019 at 2:22 AM Tom Rini <trini@konsulko.com> wrote:
>>>
>>> On Sat, Apr 27, 2019 at 10:08:34PM +0200, Simon Goldschmidt wrote:
>>>>
>>>>
>>>> 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?
>>>
>>> Ah, OK, so a new thing for my own mental checklist (which I ought to
>>> write down), there's now u-boot-custodians and u-boot-maintainers AT
>>> lists.denx.de, which are low volume custodian / maintainers only lists
>>> (they are public) to try and help avoid these "Hey, I maintain a board
>>> and just now found out I need to convert things for the next
>>> release?!?!?" problems, and similar.
>>
>> Right, I remember reading about the plan to have such lists here, but
>> I failed to find them by searching the docs in git or searching the web.
>>
>> And if I fail to find them, it could be me, but just maybe I'm not the only
>> maintainer not finding them ;-)
> 
> I emailed everyone that's listed in MAINTAINERS when the lists opened.
> I think this in part means there may be a board entry or two missing
> your email? :)

No, I'm not  a maintainer of officially supported boards. Unfortunately, 
we're having non-mainlined private boards only. And my entry as socfpga 
maintainer/co-custodioan has just been aded now ;-)

However, given the many companies out there using embedded Linux 
nowadays, I expect many such boards exist. Any while I understand we 
don't want to go into too much trouble of supporting such boards, I do 
think maintainers of such boards should be made aware of that list, too.

I guess we could note it in the toplevel README file, but finding it on 
denx.de would certainly help, too.

Regards,
Simon

  reply	other threads:[~2019-04-29 18:09 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
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 [this message]
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=5d53ee82-ffb3-a280-5a40-caadfddf92f6@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