linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akihiro TSUKADA <tskd08@gmail.com>
To: "AreMa Inc." <info@are.ma>, Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media <linux-media@vger.kernel.org>, knightrider@are.ma
Subject: Re: [PATCH 02/11] tc90522 is a client
Date: Mon, 06 Oct 2014 02:08:26 +0900	[thread overview]
Message-ID: <54317B0A.5070008@gmail.com> (raw)
In-Reply-To: <CAKnK8-REGVgdgQM+2KP0ibrf_gHMm_UO3oLr0MRoiu=-7vXUPw@mail.gmail.com>

(some Cc:'s removed, to exclude those who are not directly involved)

It seems that I should make some counterarguments.

On 2014年10月05日 21:39, AreMa Inc. wrote:
....
> We started developing and publishing PT3 drivers (chardev and DVB versions)
> on 2013 and have been submitting the patches to this community since then.
> We were waiting for reviews.

you haven't annouced any intent to merge this github project
to the linux kernel until this April.
It also has not acquired so many users that a bug in parallel streaming
had been left unnoticed until just recently.
So I disagree that your project is
> a de facto standard,
> well tested without any major/minor issues
> reported
, but it's a small thing anyway, comparted to the other claims by you.

I read your first post this April in the ML,
and exchanged some private emails after sending my reply to the ML,
about the reviews on the original post.
I waited 3 months, expecting you revise and re-post the patch,
but you didn't.

As I knew that your code did not well conform to the current DVB
driver model/style nor kernel patch submission rules,
I sent a private email that I was afraid that the patch you sent
to the ML would not be accepted if left as it is,
and asked if you would continue revising it, and if not,
I would take over the submitting of PT3 driver.
But you replied that you were reluctant to change the original code
and clealy rejected some of the reviews incl. separating of the patch.

I still waited one more week expecting you to revise the patch or
at least express some counterarguments on the ML, but no responses.
Thus I figured that you don't have a will to revise the patch anymore
and gave up merging it, so I post my code with reference to your patch.
But you didn't repsoned anything, again.

> However this July, a man named Tsukada, who has been annoying us since
> the beginning of development (we invited him to merge/join the project,
> in other words, opted him to be co-author), interrupted our submission
> and started
> speaking ill of us that we didn't want to split the driver and stopped
> the development, etc.
plz don't lie. you just said that you would accept patches to your origianl
code base at github if I would sent those.
Never mentioned joining the project or co-writing.
and I never spoke ill of you.
I just pointed out the reason why I took over the driver,
which is just same as you mentioned in the above paragraph.

If you had an objection to my patch,
Why you didn't express objections for well more than one month after my first post?
Why you didn't respond to the first review to your patch for more than 3 months?
Did you remember that you even "DECLINED" separting your patch later in September?
(see 1409966878-22627-1-git-send-email-knightrider@are.ma in the ML)

As I said in the private email to you, all those things made me believe that
you would not update your patch to conform to the DVB driver model
and thus it would not be accepted in the future,
and that you had admitted my patch since you did not express any objections.
--
akihiro

  parent reply	other threads:[~2014-10-05 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  8:59 [PATCH 00/11] pt3: pci, tc90522, mxl301rf, qm1d1c0042 Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 01/11] tc90522: better chip description Буди Романто, AreMa Inc
2014-10-05 11:20   ` Mauro Carvalho Chehab
2014-10-05  8:59 ` [PATCH 02/11] tc90522 is a client Буди Романто, AreMa Inc
2014-10-05 11:33   ` Mauro Carvalho Chehab
2014-10-05 12:39     ` AreMa Inc.
2014-10-05 13:20       ` Mauro Carvalho Chehab
2014-10-05 14:16         ` AreMa Inc.
2014-10-05 17:08       ` Akihiro TSUKADA [this message]
2014-10-05  8:59 ` [PATCH 03/11] tc90522: use hardware algorithm & correct CNR Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 04/11] pt3: add comment Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 05/11] pt3: merge I2C & DMA handlers Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 06/11] pt3: namespace cleanup Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 07/11] mxl301rf: " Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 08/11] qm1d1c0042: " Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 09/11] mxl301rf: namespace cleanup & remodelling Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 10/11] qm1d1c0042: " Буди Романто, AreMa Inc
2014-10-05  8:59 ` [PATCH 11/11] pt3: merge I2C & DMA handlers Буди Романто, AreMa Inc

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=54317B0A.5070008@gmail.com \
    --to=tskd08@gmail.com \
    --cc=info@are.ma \
    --cc=knightrider@are.ma \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@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;
as well as URLs for NNTP newsgroup(s).