From: Nick Clifton <nickc@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Mihails Strasuns <mihails.strasuns@intel.com>,
gdb-patches@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/5] bfd: add elfcore_write_file_note
Date: Mon, 25 Jan 2021 11:04:58 +0000 [thread overview]
Message-ID: <62ec3fd4-404c-c84f-fe12-4bdef212ce0d@redhat.com> (raw)
In-Reply-To: <618186a8-b1c4-43b8-ff06-46c1d520d5d0@polymtl.ca>
Hi Simon,
> Adding binutils@ in CC, can someone over there please review this change?
>> bfd/ChangeLog:
>> 2020-12-17 Mihails Strasuns <mihails.strasuns@intel.com>
>>
>> * bfd-elf.h (elfcore_write_file_note): New function.
>> * elf.c (elfcore_write_file_note): New function.
This part of the change is totally fine. Please consider it approved.
Cheers
Nick
prev parent reply other threads:[~2021-01-25 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210103130300.21637-1-mihails.strasuns@intel.com>
[not found] ` <20210103130300.21637-2-mihails.strasuns@intel.com>
2021-01-22 22:17 ` Simon Marchi
2021-01-25 11:04 ` Nick Clifton [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=62ec3fd4-404c-c84f-fe12-4bdef212ce0d@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=mihails.strasuns@intel.com \
--cc=simon.marchi@polymtl.ca \
/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).