From: Alejandro Colomar <alx@kernel.org>
To: rajesh <r.pandian@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Contributing to documentation
Date: Fri, 22 Dec 2023 15:20:21 +0100 [thread overview]
Message-ID: <ZYWbJXjbQDm-2V8H@debian> (raw)
In-Reply-To: <CAKkEDkX_kw=5rwn5qcbt45RjWMtSuVNAzYDc2MEkaTr0FwQe3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Hi rajesh,
On Fri, Dec 22, 2023 at 07:40:19PM +0530, rajesh wrote:
> Thanks, I'll check them out Alejandro. Yes I m ok with git (but
> looking forward to learn more)
Ok.
> I also made a comment on https://bugzilla.kernel.org/show_bug.cgi?id=218266
>
> Does my comment looks ok? The language,
Yes, the language looks good.
> code etc,.? If it's ok then
> putting this code in shutdown makes sense?
That code is useful for debugging with something short, but normally you
shouldn't call printf(3) from a signal handler.
<https://stackoverflow.com/questions/16891019/how-to-avoid-using-printf-in-a-signal-handler>
I can't give any other response without actually investigating myself,
since I don't use signal handlers often.
Have a lovely day,
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-22 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKkEDkWv_wksbcAkUEaFdAQhkhZH1xr+pLidXAvKvV-ka7gE1Q@mail.gmail.com>
[not found] ` <CAKkEDkU28SRY-dZOVdnGORV2f8ovOak1b=Pr8+bEFDb-B2vx+A@mail.gmail.com>
2023-12-22 10:47 ` Contributing to documentation Alejandro Colomar
2023-12-22 14:10 ` rajesh
2023-12-22 14:20 ` Alejandro Colomar [this message]
2023-12-22 15:08 ` rajesh
2023-12-22 16:47 ` Alejandro Colomar
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=ZYWbJXjbQDm-2V8H@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=r.pandian@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.