LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Santosh Shilimkar <ssantosh@kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v2 0/4] ARM: davinci: remove the mach-specific aemif driver - part 1
Date: Tue, 17 Apr 2018 15:59:10 +0200 [thread overview]
Message-ID: <CAMpxmJVa8xCsru4ixBxMmZe4_aDyiuPvfd_wgUTckG5jWahe1g@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Me6b0e+d6QRTdr7G9zLdqonjxLBp6h6bM_JaF8OytR=QA@mail.gmail.com>
2018-04-17 14:41 GMT+02:00 Bartosz Golaszewski <brgl@bgdev.pl>:
> 2018-04-17 14:36 GMT+02:00 Bartosz Golaszewski <bgolaszewski@baylibre.com>:
>> 2018-04-17 12:53 GMT+02:00 Sekhar Nori <nsekhar@ti.com>:
>>> Hi Bartosz,
>>>
>>> On Tuesday 17 April 2018 03:59 PM, Bartosz Golaszewski wrote:
>>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>>
>>>> This is the first part of changes required to remove duplicate aemif
>>>> support from mach-davinci.
>>>>
>>>> I actually noticed that one of my previous changes from 2017 broke nand
>>>> in legacy mode - the clock lookup no longer works. This series addresses
>>>> it as well.
>>>>
>>>> First patch just uses a static string for the ti-aemif driver name.
>>>>
>>>> The second adds support for board files to the aemif driver.
>>>>
>>>> Last two add nand support to da850-lcdk in legacy mode and make
>>>> da850-evm use the platform driver instead of the mach-specific one.
>>>>
>>>> If these patches get accepted, I'll prepere a follow-up moving all
>>>> other boards to the new platform driver.
>>>>
>>>> This series applies on top of v8 of David Lechner's CCF series.
>>>
>>> Are there any patches in the series that can safely be applied to v4.17-rc1?
>>>
>>> Thanks,
>>> Sekhar
>>
>> Hi Sekhar,
>>
>> yes, all of them. They're not linked to David's work in any way.
>>
>> Bart
>
> Oops, -ETOOFAST, I rebased it on top of David's v9, let me check how
> it works with mainline - it should be mostly fine.
>
> Bart
Ok, so the patches apply and build nicely on top of v4.17-rc1, but
they only actually work with David's v9 branch. On the other hand nand
doesn't work with mainline now anyway so I assume it's safe to apply
them and wait for David's patches to be merged.
Thanks,
Bartosz
next prev parent reply other threads:[~2018-04-17 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:29 [RESEND PATCH v2 0/4] ARM: davinci: remove the mach-specific aemif driver - part 1 Bartosz Golaszewski
2018-04-17 10:29 ` [RESEND PATCH v2 1/4] memory: aemif: don't rely on kbuild for driver's name Bartosz Golaszewski
2018-04-17 10:29 ` [RESEND PATCH v2 2/4] memory: aemif: add support for board files Bartosz Golaszewski
2018-04-17 13:57 ` Sekhar Nori
2018-04-17 10:29 ` [RESEND PATCH v2 3/4] ARM: davinci: add aemif & nand support to da850-lcdk in legacy mode Bartosz Golaszewski
2018-04-17 14:09 ` Sekhar Nori
2018-04-25 9:14 ` Bartosz Golaszewski
2018-04-25 9:20 ` Sekhar Nori
2018-04-17 10:29 ` [RESEND PATCH v2 4/4] ARM: davinci: use aemif platform driver in legacy mode for da850-evm Bartosz Golaszewski
2018-04-17 14:12 ` Sekhar Nori
2018-04-25 9:26 ` Bartosz Golaszewski
2018-04-17 10:53 ` [RESEND PATCH v2 0/4] ARM: davinci: remove the mach-specific aemif driver - part 1 Sekhar Nori
2018-04-17 12:36 ` Bartosz Golaszewski
2018-04-17 12:41 ` Bartosz Golaszewski
2018-04-17 13:59 ` Bartosz Golaszewski [this message]
2018-04-17 17:29 ` Santosh Shilimkar
2018-04-18 8:17 ` Sekhar Nori
2018-04-18 17:15 ` Santosh Shilimkar
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=CAMpxmJVa8xCsru4ixBxMmZe4_aDyiuPvfd_wgUTckG5jWahe1g@mail.gmail.com \
--to=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=ssantosh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).