linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/exynos: Remove driver
Date: Mon, 10 Mar 2014 00:48:28 +0100	[thread overview]
Message-ID: <531CFDCC.5020302@gmail.com> (raw)
In-Reply-To: <CAHQjnOP=cq4+wxjuOzKKHmp2vC1DUTwogiQkL=8NtNWZiBJ4jg@mail.gmail.com>

Hi KyongHo,

On 09.03.2014 14:54, KyongHo Cho wrote:
> On Thu, Mar 6, 2014 at 8:48 AM, Kyungmin Park <kmpark@infradead.org> wrote:
>> On Fri, Feb 14, 2014 at 9:17 AM, Cho KyongHo <pullip.cho@samsung.com> wrote:
>>>> -----Original Message-----
>>>> From: Olof Johansson [mailto:olof at lixom.net]
>>>> Sent: Friday, February 14, 2014 4:34 AM
>>>>
>>>> On Mon, Feb 10, 2014 at 10:21 PM, Kukjin Kim <kgene.kim@gmail.com> wrote:
>>>>
>>>>> Just adding KyongHo Cho.
>>>>>
>>>>> If he can fixup for this time, it would be best solution because he knows
>>>>> well than others, I think.
>>>>
>>>> It's not so much a matter of "fixup for this time", it's a about
>>>> having ownership of the driver, making sure it works (and keeps
>>>> working if there is related development). The posted patches have not
>>>> been followed through on and the result is a broken driver. :(
>>>>
>>>> I definitely appreciate his expertise, and we should make sure that he
>>>> gets to review the code, but if someone else is able to spend time on
>>>> reworking the driver (or rewriting a newer one) and maintaining it
>>>> longer-term, then we should not stop them from doing so. And there is
>>>> no reason to keep broken stale code in the kernel meanwhile.
>>>>
>>>
>>> Thank you for your concerning.
>>> I also definitely agree with you that the driver must work.
>>> I am always concerning about it but it was not easy to make some time
>>> for the patches.
>>>
>>> I will continue to post the next version of patches, of course.
>>> I think it is not far from now to show it.
>>
>> Lots of time is going from last reply. there are two options.
>> 1. just waiting more
>> 2. remove it as patch and start it again by someone.
>>
>> what's the opinions?
>>
>
> Please be patient until the patches are OK enough to post.
>
> The patches have lots of improvements and workarounds.
>
> Sorry for delaying the patches.
>
> One thing is certain, starting from scratch is not a good idea.
> Why not discuss with me to make exynos-iommu driver better?

It is not a matter of starting from scratch or not, but rather of 
getting a reasonable IOMMU driver for Exynos in mainline in reasonable 
period of time. Usually it is much easier to just remove a stale driver 
and quickly refactor all the code at once and then add a "new" driver, 
than wasting time on submitting heaps of patches for a driver that is 
not used and does not work anyway.

In fact, we already have a working driver, based on heavily refactored 
original one in our internal tree anyway and we are just wasting time on 
waiting for next version of the original refactor series to come, while 
we could simply drop current version from the kernel, squash all of any 
changes to it into a one patch adding the new driver and submit it 
instead. Of course care would be taken to preserve any authorship 
information.

Do you have some time frame in which you may post next version of the 
series (and guaranteed time to work on it)?

Best regards,
Tomasz

      reply	other threads:[~2014-03-09 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 19:51 [PATCH] iommu/exynos: Remove driver Olof Johansson
2014-02-07  4:26 ` Inki Dae
     [not found]   ` <CAH9JG2Xoz1_Y7CV6FUiGAO9o5T7jtFUYqJpcAysLttwu4527zQ@mail.gmail.com>
2014-02-07 13:49     ` Marek Szyprowski
     [not found]       ` <CAL5jtJmfwajFD0cnYt6gOfFsZ5hGbFi=5kv8g4x23fY6qGBOew@mail.gmail.com>
2014-02-13 19:33         ` Olof Johansson
2014-02-14  0:17           ` Cho KyongHo
2014-03-05 23:48             ` Kyungmin Park
2014-03-09 13:54               ` KyongHo Cho
2014-03-09 23:48                 ` Tomasz Figa [this message]

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=531CFDCC.5020302@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).