public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: 瞿仙淼 <xianmiao.qxm@alibaba-inc.com>
Cc: newlib <newlib@sourceware.org>
Subject: Re: [PATCH] libgloss: csky: use atexit to call fini-array functions.
Date: Fri, 13 Jan 2023 11:11:52 +0100	[thread overview]
Message-ID: <Y8EuaDGHck72iTwL@calimero.vinschen.de> (raw)
In-Reply-To: <41528e9f-1b8c-4ca0-a2bd-1341e683dca8.xianmiao.qxm@alibaba-inc.com>

Hi Cooper,

On Jan 13 10:07, 瞿仙淼 wrote:
> Hi,
> Could someone review this patch? This is a small change, I would
> appreciate it if anyone would like to review.

your original mail didn't make it to the newlib ML, I don't see this in
the archives @ https://sourceware.org/pipermail/newlib/2023/ either.

Can you resend your patch with `git send-email' or as attachment?

But see below.

> ------------------------------------------------------------------
> From:Xianmiao Qu <cooper.qu@linux.alibaba.com>
> Sent At:2023 Jan. 10 (Tue.) 15:59
> To:newlib <newlib@sourceware.org>
> Cc:Xianmiao Qu <cooper.qu@linux.alibaba.com>
> Subject:[PATCH] libgloss: csky: use atexit to call fini-array functions.
> __libc_fini_array should be called upon exit to call the
> global termination functions in fini-array, use atexit to
> register it at __start.

There should be an empty line between the first and the second line of
the commit message.  The text up to the first blank line in a commit
message is treated as the commit title and your message results in a multi
line summary.

Other than that, your patch looks goot to me.


Thanks,
Corinna


  reply	other threads:[~2023-01-13 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230110075927.1937-1-cooper.qu@linux.alibaba.com>
2023-01-13  2:07 ` 瞿仙淼
2023-01-13 10:11   ` Corinna Vinschen [this message]
2023-01-13 12:46 Xianmiao Qu
2023-01-13 13:10 ` Corinna Vinschen

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=Y8EuaDGHck72iTwL@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=newlib@sourceware.org \
    --cc=xianmiao.qxm@alibaba-inc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).