qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 4/9] linux-user/nios2 linux-user/riscv: Clean up header guards
Date: Mon, 13 May 2019 17:58:55 +0100	[thread overview]
Message-ID: <CAFEAcA-qpxBS0HxD4xoEhGAjVTzHZC9e6TsSyb25C2HY2HseTw@mail.gmail.com> (raw)
In-Reply-To: <mhng-5f5db13d-9ab7-414b-8979-4e119c319f78@palmer-si-x1e>

On Mon, 13 May 2019 at 17:56, Palmer Dabbelt <palmer@sifive.com> wrote:
>
> On Mon, 13 May 2019 01:18:39 PDT (-0700), armbru@redhat.com wrote:
> > Reuse of the same guard symbol in multiple headers is okay as long as
> > they cannot be included together.  scripts/clean-header-guards.pl
> > can't tell, so it warns.
> >
> > Since we can avoid guard symbol reuse easily, do so: use guard symbol
> > ${target^^}_${fname^^} for linux-user/$target/$fname, just like we did
> > in commit a9c94277f0..3500385697.
> >
> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
> > Message-Id: <20190315145123.28030-4-armbru@redhat.com>
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

> Reviewed-by: Palmer Dabbelt <palmer@sifive.com>
>
> I'm assuming this is going in through someone else's tree, so I'm not going to
> pick it up into mine.

The subject line says "PULL" rather than "PATCH", so it is
already going into master (indeed I just applied it).
In general there's not much point in commenting on
patches in pull requests on the lists except for "this
has a problem, please don't apply it" feedback. (In that
case you should reply to the cover letter, because I won't
necessarily see replies to individual patches in the pull
before I apply the pull.)

thanks
-- PMM


  reply	other threads:[~2019-05-13 17:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13  8:18 [Qemu-devel] [PULL 0/9] Miscellaneous patches for 2019-05-13 Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 1/9] Clean up includes Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 2/9] Use #include "..." for our own headers, <...> for others Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 3/9] authz: Normalize #include "authz/trace.h" to "trace.h" Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 4/9] linux-user/nios2 linux-user/riscv: Clean up header guards Markus Armbruster
2019-05-13 16:55   ` Palmer Dabbelt
2019-05-13 16:58     ` Peter Maydell [this message]
2019-05-13  8:18 ` [Qemu-devel] [PULL 5/9] target/xtensa: Clean up core-isa.h " Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 6/9] Clean up header guards that don't match their file name Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 7/9] Clean up ill-advised or unusual header guards Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 8/9] Normalize header guard symbol definition Markus Armbruster
2019-05-13  8:18 ` [Qemu-devel] [PULL 9/9] Clean up decorations and whitespace around header guards Markus Armbruster
2019-05-13 15:41 ` [Qemu-devel] [PULL 0/9] Miscellaneous patches for 2019-05-13 Peter Maydell

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=CAFEAcA-qpxBS0HxD4xoEhGAjVTzHZC9e6TsSyb25C2HY2HseTw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=armbru@redhat.com \
    --cc=palmer@sifive.com \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).