From: Jeff Law <law@redhat.com>
To: marxin <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Cc: hrishikeshparag@gmail.com, hubicka@ucw.cz
Subject: Re: [PATCH 3/3] Fix GNU coding style in lto-common.c.
Date: Mon, 29 Apr 2019 19:43:00 -0000 [thread overview]
Message-ID: <716dba30-d3e2-385d-6e93-354c85995a75@redhat.com> (raw)
In-Reply-To: <f38080030fc43ca5408f20f8b92d23b548561efd.1552571776.git.mliska@suse.cz>
On 3/14/19 7:02 AM, marxin wrote:
>
> gcc/lto/ChangeLog:
>
> 2019-03-14 Martin Liska <mliska@suse.cz>
>
> * lto-common.c: Update coding style.
> * lto.c (materialize_cgraph): Likewise.
> ---
> gcc/lto/lto-common.c | 214 ++++++++++++++++++++++---------------------
> gcc/lto/lto.c | 30 +++---
> 2 files changed, 128 insertions(+), 116 deletions(-)
>
OK once the others have gone in.
jeff
next prev parent reply other threads:[~2019-04-29 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 14:00 [PATCH 0/3][stage1] [PATCH v2] LTO dump tool marxin
2019-03-14 14:00 ` [PATCH 2/3] Add lto-dump tool marxin
2019-04-26 13:14 ` Richard Biener
2022-10-28 10:14 ` Thomas Schwinge
2022-10-29 3:22 ` Jeff Law
2019-03-14 14:00 ` [PATCH 3/3] Fix GNU coding style in lto-common.c marxin
2019-04-29 19:43 ` Jeff Law [this message]
2019-03-14 14:06 ` [PATCH 1/3] Split part of functionality from lto.c to lto-common.c marxin
2019-04-26 12:47 ` Richard Biener
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=716dba30-d3e2-385d-6e93-354c85995a75@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hrishikeshparag@gmail.com \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
/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).