From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: Zap lpc32xx_ssp driver-related code
Date: Sun, 21 Apr 2019 14:43:24 -0400 [thread overview]
Message-ID: <20190421184324.GL4664@bill-the-cat> (raw)
In-Reply-To: <20190419064859.7744-1-jagan@amarulasolutions.com>
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!
--
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/20190421/d38cb1c6/attachment.sig>
next prev parent reply other threads:[~2019-04-21 18:43 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 [this message]
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
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=20190421184324.GL4664@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 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.