Linux IOMMU Development
 help / color / mirror / Atom feed
From: Cho KyongHo <pullip.cho@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>, 'Kukjin Kim' <kgene.kim@gmail.com>
Cc: 'Marek Szyprowski' <m.szyprowski@samsung.com>,
	'Kyungmin Park' <kmpark@infradead.org>,
	'Inki Dae' <inki.dae@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
	'Joerg Roedel' <joro@8bytes.org>,
	iommu@lists.linux-foundation.org,
	'Sean Paul' <seanpaul@chromium.org>,
	'Tomasz Figa' <t.figa@samsung.com>,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] iommu/exynos: Remove driver
Date: Fri, 14 Feb 2014 09:17:25 +0900	[thread overview]
Message-ID: <001301cf291a$233fdc70$69bf9550$@samsung.com> (raw)
In-Reply-To: <CAOesGMhH2WHvkaobewdnPeiThrWTfw0m4WWAZW98-iS2xdr+ow@mail.gmail.com>

> -----Original Message-----
> From: Olof Johansson [mailto:olof@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.

Regards,

Ky0ongHo

  reply	other threads:[~2014-02-14  0:17 UTC|newest]

Thread overview: 10+ 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]   ` <CAAQKjZMo6=dtur6NfvDY9=jVF=7VxHub=isnEwPw0+RKCq6xAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-07 12:44     ` Kyungmin Park
2014-02-07 13:49       ` Marek Szyprowski
     [not found]         ` <52F4E481.3050902-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-02-11  6:21           ` Kukjin Kim
2014-02-13 19:33             ` Olof Johansson
2014-02-14  0:17               ` Cho KyongHo [this message]
2014-03-05 23:48                 ` Kyungmin Park
2014-03-09 13:54                   ` KyongHo Cho
2014-03-09 23:48                     ` Tomasz Figa

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='001301cf291a$233fdc70$69bf9550$@samsung.com' \
    --to=pullip.cho@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=inki.dae@samsung.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kgene.kim@gmail.com \
    --cc=kmpark@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=olof@lixom.net \
    --cc=seanpaul@chromium.org \
    --cc=t.figa@samsung.com \
    /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