[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240530203149.1fe881ed@coco.lan>
Date: Thu, 30 May 2024 20:31:49 +0200
From: Mauro Carvalho Chehab <mchehab@...nel.org>
To: YongSu Yoo <yongsuyoo0215@...il.com>
Cc: Markus Elfring <Markus.Elfring@....de>, linux-media@...r.kernel.org,
Hyunwoo Kim <v4bel@...ori.io>, LKML <linux-kernel@...r.kernel.org>, Dan
Carpenter <dan.carpenter@...aro.org>
Subject: Re: [PATCH] media: dvb_ca_en50221: Add a returing EBUSY logic into
CA_RESET
Em Tue, 28 May 2024 21:14:37 +0900
YongSu Yoo <yongsuyoo0215@...il.com> escreveu:
> Dear Markus Elfring
Please don't top-post. Makes hard to follow the comments.
>
>
> 2024년 5월 28일 (화) 오후 2:38, Markus Elfring <Markus.Elfring@....de>님이 작성:
>
> >
> > …
> > > For preventing this problem from happening, we make CA_RESET ioctl do
> > > nothing and only return EBUSY if the ioctl is called during the
> > > "transiting" states.
> >
> > Would you like to avoid any typos (in the summary phrase)?
> Initially, I sent this E-mail using the below command
> "....git send-email --to mchehab@...nel.org,
> linux-media@...r.kernel.org, xxxxxxxxxxx.patch. ..."
Git send-email is a good way to send patches. You may also use
a decent e-mail client that won't mangle with whitespaces. I use
myself claws-mail; other develpers use emacs. Feel free to pick your
poison, but if the email doesn't handle whitespaces well and/or
don't allow writing the answers below the original comments (instead
of top-posting), it shouldn't be used.
> In response to what you suggested, is it OK if I use Gmail and attach
> a new patch ?
No. Never attach a patch as the mailing list will reject, and if not,
patchwork.linuxtv.org won't pick it.
You may use gmail, if you setup your e-mail client to use it as a
SMTP server. Using webmail solutions typically won't work open source
discussions, as it does lots of wrong things, like top-posting, not
honoring 80 columns on emails and/or mangling tabs and white spaces.
Thanks,
Mauro
Powered by blists - more mailing lists