[U-Boot] [PATCH] spi: Zap lpc32xx_ssp driver-related code

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:47:28 -0400	[thread overview]
Message-ID: <20190424114728.GC31207@bill-the-cat> (raw)
In-Reply-To: <CAMty3ZCwUqDNOnDtXmTLhE-YDa6XNgCmz4qViuzvL4dxvjdGsQ@mail.gmail.com>

On Wed, Apr 24, 2019 at 01:11:02PM +0530, Jagan Teki wrote:
> On Mon, Apr 22, 2019 at 12:13 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Fri, Apr 19, 2019 at 12:18:59PM +0530, 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
> > > - no response for dm converted patch
> > > - driver-model migration expiry
> > >
> > > Cc: Vladimir Zapolskiy <vz@mleia.com>
> > > Cc: Albert ARIBAUD <albert.aribaud@3adev.fr>
> > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> >
> > For all of the "drop" patches you sent, can you please re-work them to
> > instead make the relevant option instead depend on BROKEN for now and
> > we'll drop the code after this next release?  Thanks!
> 
> This was my initial plan before indicating the warnings on Makefile in
> previous releases, do we really need this and prolong the migration
> plan further?

We absolutely do because as you can see we're still just now having
people see this deadline for the first time because we did a bad job
communicating about it.

-- 
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/0fd9e46d/attachment.sig>