From: Eduardo Habkost <ehabkost@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, qemu-devel@nongnu.org,
ccarrara@redhat.com, crosa@redhat.com
Subject: Re: [Qemu-devel] [PATCH] target/i386: Fixes to the check missing features routine
Date: Tue, 11 Dec 2018 14:55:10 -0200 [thread overview]
Message-ID: <20181211165510.GF7141@habkost.net> (raw)
In-Reply-To: <5cd0b649-c74f-877d-4b5d-a0943a04c7eb@redhat.com>
On Tue, Dec 11, 2018 at 02:40:33PM -0200, Wainer dos Santos Moschetta wrote:
[...]
> > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > index f81d35e1f9..2502a3adda 100644
> > > --- a/target/i386/cpu.c
> > > +++ b/target/i386/cpu.c
> > > @@ -3615,19 +3615,29 @@ static void x86_cpu_class_check_missing_features(X86CPUClass *xcc,
> > > x86_cpu_filter_features(xc);
> > > + /* Uses an auxiliar dictionary to ensure the list of features has not
> > > + repeated name. */
> > > + QDict *unique_feats_dict = qdict_new();
> > Multiline comments are formatted this way:
> >
> > /*
> > * like
> > * this
> > */
> >
> > (See CODING_STYLE for details)
>
> scripts/checkpatch.pl did not catch it. Should it?
It should, we just need a volunteer who understands Perl to fix
that. :)
--
Eduardo
prev parent reply other threads:[~2018-12-11 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 22:14 [Qemu-devel] [PATCH] target/i386: Fixes to the check missing features routine Wainer dos Santos Moschetta
2018-12-07 22:26 ` Eric Blake
2018-12-10 1:06 ` Caio Carrara
2018-12-10 16:46 ` Eduardo Habkost
2018-12-11 16:40 ` Wainer dos Santos Moschetta
2018-12-11 16:55 ` Eduardo Habkost [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=20181211165510.GF7141@habkost.net \
--to=ehabkost@redhat.com \
--cc=ccarrara@redhat.com \
--cc=crosa@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=wainersm@redhat.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.