From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] spi: Zap mxs_spi driver-related code
Date: Fri, 19 Apr 2019 15:37:34 +0200 [thread overview]
Message-ID: <8d3b4bf3-34f0-b66c-880a-e046f402ab0f@denx.de> (raw)
In-Reply-To: <3b1d49ec-1a6c-b6a1-97f1-46833e9d7ea5@denx.de>
On 4/19/19 3:29 PM, Marek Vasut wrote:
> On 4/19/19 2:42 PM, Tom Rini wrote:
>> On Fri, Apr 19, 2019 at 11:25:47AM +0200, Marek Vasut wrote:
>>> On 4/19/19 8:55 AM, Jagan Teki wrote:
>>>> Dropped
>>>> - mxs_spi driver
>>>> - CONFIG_MXS_SPI
>>>>
>>>> Dropped due to:
>>>> - no active updates
>>>> - no dm conversion
>>>> - multiple pings for asking dm-conversion
>>>
>>> This is the first information I received ... sigh.
>>
>> Sigh, I thought you had seen this before and noted at the time that you
>> hadn't heard anything before then.
>>
>> So, are the mx28 family boards something we still want to support? I
>> assume there's going to be other things that need converting there too.
>
> I didn't see much MX28 activity recently myself, except for the thing
> Mans was playing with.
Oh and regarding the conversion, yes, a lot of MXS stuff will need
conversion.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-04-19 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 6:55 [U-Boot] [PATCH v3] spi: Zap mxs_spi driver-related code Jagan Teki
2019-04-19 9:25 ` Marek Vasut
2019-04-19 12:42 ` Tom Rini
2019-04-19 13:29 ` Marek Vasut
2019-04-19 13:37 ` Marek Vasut [this message]
2019-04-19 13:32 ` Michael Nazzareno Trimarchi
2019-04-21 18:41 ` Tom Rini
2019-04-21 19:02 ` Marek Vasut
2019-04-24 6:49 ` Jagan Teki
[not found] ` <yw1x7ebjydcy.fsf@denx.de>
2019-04-24 9:44 ` Michael Nazzareno Trimarchi
2019-04-24 11:50 ` Tom Rini
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=8d3b4bf3-34f0-b66c-880a-e046f402ab0f@denx.de \
--to=marex@denx.de \
--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.