From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: Zap lpc32xx_ssp driver-related code
Date: Wed, 24 Apr 2019 07:48:43 -0400 [thread overview]
Message-ID: <20190424114843.GD31207@bill-the-cat> (raw)
In-Reply-To: <CAMty3ZC=akSJkKa2hRyT8=UHQuW4Z1=iUTit30tNiN+0zzsDuw@mail.gmail.com>
On Wed, Apr 24, 2019 at 12:14:07PM +0530, Jagan Teki wrote:
> On Tue, Apr 23, 2019 at 2:20 AM Vladimir Zapolskiy <vz@mleia.com> 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'.
>
> Here is the number iterations around the ML, this indeed a
> notification for dm-conversion.
> [1] [2][4][5]
>
> >
> > > - no response for dm converted patch
> >
> > I believe there was no DM conversion patch for this particular driver,
> > could it happen that I've missed it?
>
> [3]
>
> [1] https://patchwork.ozlabs.org/patch/1002858/
> [2] https://patchwork.ozlabs.org/patch/1000463/
> [3] https://patchwork.ozlabs.org/patch/910751/
> [4] https://gitlab.incom.co/CM-Shield/u-boot/commit/c4e68d3aa8178f6aa63a79c4f8f459c0e3ed58e8?view=parallel
> [5] https://lists.denx.de/pipermail/u-boot/2018-March/322135.html
And to be clear and repeat myself, in all of the above cases while it
did go to the ML it did not to/cc nearly enough (or in some cases I seem
to recall, any) people directly responsible for the platforms in
question. I should have caught that and spoken up more at the time,
sorry.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190424/a2ec02c9/attachment.sig>
next prev parent reply other threads:[~2019-04-24 11:48 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
2019-04-24 6:44 ` Jagan Teki
2019-04-24 11:48 ` Tom Rini [this message]
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=20190424114843.GD31207@bill-the-cat \
--to=trini@konsulko.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