linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Soeren Moch <smoch@web.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Regression 5.14] media: dvb userspace api
Date: Sat, 21 Aug 2021 19:28:54 +0530	[thread overview]
Message-ID: <CAHFNz9+2rQ+kGDM1m5mkZ9CjNjWqMsZxWQ8=i2=6UtKh0vQUrA@mail.gmail.com> (raw)
In-Reply-To: <20210819133128.45ef4353@coco.lan>

Dearest Mauro,

I am not trying to annoy you or anyone else with my response here, but:


On Thu, Aug 19, 2021 at 5:01 PM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Em Wed, 11 Aug 2021 14:15:02 +0200
> Soeren Moch <smoch@web.de> escreveu:
>
> > Commit 819fbd3d8ef36c09576c2a0ffea503f5c46e9177 ("media: dvb header
> > files: move some headers to staging") moved audio, video, and osd parts
> > of the media DVB API to staging and out of kernel headers. But this is
> > part of the media userspace API, removing this causes regressions.
>
> There's no regression: a legacy driver (av7110) for a device that stopped
> being manufactured 15 years ago and that doesn't work anymore with current
> Digital TV transmissions was removed, together with the API that it was
> implemented inside such driver's code.


Please do not exaggerate..
(I can write more precise technical details in here, but that will not solve the
real issue at hand.)

You have only your own viewpoint, refuse to listen to anyone else. Wonder
why all the DVB developers left development ? It's all about you, yourself
and you. Linus doesn't care about anything else, you have been very lucky!

You need serious introspection about yourself. Take a deep breath, think for
yourself, why I stopped submitting code. Forget myself, think about the list
of developers who were around, but not now.

People need to have fun with what they are doing, but you make it, everything
about yourself. It's all about maintaining connections, rather than destroying
them. At least during these uncertain times, please stop the narrow thinking.

If you find my view offending, just ignore it, no need to give another thousand
mile long essay; I am on my way ..

Friendly Regards,
MA

  reply	other threads:[~2021-08-21 13:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 12:15 [Regression 5.14] media: dvb userspace api Soeren Moch
2021-08-19 11:31 ` Mauro Carvalho Chehab
2021-08-21 13:58   ` Manu Abraham [this message]
2021-08-22 15:21   ` Soeren Moch
2021-08-22 17:47     ` Mauro Carvalho Chehab
2021-08-23 14:59       ` Soeren Moch
2021-08-23 16:58         ` Linus Torvalds
2021-08-23 20:16           ` Soeren Moch
2021-08-24  7:47           ` Mauro Carvalho Chehab
2021-08-24 20:01             ` Honza P
2021-08-25  2:55           ` Manu Abraham
2021-08-25  6:33             ` Mauro Carvalho Chehab
2021-08-25 16:16               ` Manu Abraham
2021-08-26 12:26                 ` Mauro Carvalho Chehab

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='CAHFNz9+2rQ+kGDM1m5mkZ9CjNjWqMsZxWQ8=i2=6UtKh0vQUrA@mail.gmail.com' \
    --to=abraham.manu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=smoch@web.de \
    --cc=torvalds@linux-foundation.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).