From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: YongSu Yoo <yongsuyoo0215@gmail.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
linux-media@vger.kernel.org, Hyunwoo Kim <v4bel@theori.io>,
LKML <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] media: dvb_ca_en50221: Add a returing EBUSY logic into CA_RESET
Date: Thu, 30 May 2024 20:31:49 +0200 [thread overview]
Message-ID: <20240530203149.1fe881ed@coco.lan> (raw)
In-Reply-To: <CANXPkT5ggr8VbYdRy+uSnfHxDRES5arJJ8p+ist1CBTm-1xaUQ@mail.gmail.com>
Em Tue, 28 May 2024 21:14:37 +0900
YongSu Yoo <yongsuyoo0215@gmail.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@web.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@kernel.org,
> linux-media@vger.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
next prev parent reply other threads:[~2024-05-30 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 12:13 [PATCH] media: dvb_ca_en50221: Add a returing EBUSY logic into CA_RESET yongsuyoo0215
2024-04-11 12:02 ` YongSu Yoo
2024-05-01 7:54 ` YongSu Yoo
2024-05-23 13:16 ` YongSu Yoo
2024-05-27 10:56 ` Dan Carpenter
2024-05-27 13:32 ` YongSu Yoo
2024-05-28 5:37 ` Markus Elfring
2024-05-28 12:14 ` YongSu Yoo
2024-05-28 12:35 ` Markus Elfring
2024-05-30 18:31 ` Mauro Carvalho Chehab [this message]
[not found] ` <CANXPkT6wxEzX=Seyi-SctkpN17AgeTAWSPr-Yt2kRzD_isAa2g@mail.gmail.com>
2025-02-01 8:24 ` [PATCH] " Mauro Carvalho Chehab
2025-02-01 13:01 ` 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=20240530203149.1fe881ed@coco.lan \
--to=mchehab@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=v4bel@theori.io \
--cc=yongsuyoo0215@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.