From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: YongSu Yoo <yongsuyoo0215@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
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>,
yongsu.yoo@lge.com
Subject: Re: [PATCH] media: dvb_ca_en50221: Add a returing EBUSY logic into CA_RESET
Date: Sat, 1 Feb 2025 14:01:52 +0100 [thread overview]
Message-ID: <20250201140152.52109e19@foz.lan> (raw)
In-Reply-To: <20250201092427.6a09c39d@foz.lan>
Em Sat, 1 Feb 2025 09:24:27 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> Em Sat, 1 Feb 2025 09:44:18 +0900
> YongSu Yoo <yongsuyoo0215@gmail.com> escreveu:
>
> > Dear Mauro Carvalho Chehab
> >
> > I know how to send an E-mail using "....git send-email --to .."
> > But,
> > I do not know how to reply to this E-mail loop using "....git send-email
> > --to .."
> > Can you kindly guide me ?
>
> Never used git send-email to reply, as it is mainly focused on sending
> e-mails, not being a true emailer: it just sends e-mail: it doesn't
> receive. In thesis, you could download the original e-mail using b4 or lei,
> then manually write a reply text on it and use git send-email. This is
> easier said than done, as you'll need to take care of SMTP headers yourself.
> This would require some knowledge about SMTP RFCs.
>
> If I were you, I would seek for some other alternatives.
>
> Most people use mutt for Kernel work, as it is CLI. There is also alpine
> I haven't used alpine for ages, but it is a decent CLI e-mail client, using
> a very simple interface, although it has less features than mutt.
>
> I prefer instead to use claws-mail as it has a reasonable GUI, it is fast
> and it is not overbloated with features I won't use.
>
> Neither mutt, alpine or claws-mail mangle whitespaces and line breaks on
> e-mails, and they can be setup to not do top-postings.
>
> If you want something simpler, perhaps you could try notmuch[1]. I never
> tried myself, but I heard it can be used to reply to e-mails without even
> needing to subscribe to a ML.
>
> [1] https://notmuchmail.org/
>
> You may also find useful to have a SMTP relay server. Probably one of the
> simplest ones to setup is msmtp: https://marlam.de/msmtp/.
>
> I hope that helps.
Btw, there's a chapter at Kernel documentation related to e-mail
clients:
https://www.kernel.org/doc/html/latest/process/email-clients.html
>
> Regards,
> Mauro
>
>
> >
> > 2024년 5월 31일 (금) 오전 3:31, Mauro Carvalho Chehab <mchehab@kernel.org>님이 작성:
> >
> > > 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
> > >
>
>
>
> Thanks,
> Mauro
Thanks,
Mauro
prev parent reply other threads:[~2025-02-01 13:01 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 ` [PATCH] " Mauro Carvalho Chehab
[not found] ` <CANXPkT6wxEzX=Seyi-SctkpN17AgeTAWSPr-Yt2kRzD_isAa2g@mail.gmail.com>
2025-02-01 8:24 ` Mauro Carvalho Chehab
2025-02-01 13:01 ` Mauro Carvalho Chehab [this message]
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=20250201140152.52109e19@foz.lan \
--to=mchehab+huawei@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=mchehab@kernel.org \
--cc=v4bel@theori.io \
--cc=yongsu.yoo@lge.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox