From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: pmoore@redhat.com, peter.maydell@linaro.org,
Andrew Jones <drjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] libseccomp: add cacheflush to whitelist
Date: Wed, 14 Oct 2015 16:58:13 +0200 [thread overview]
Message-ID: <20151014145813.GA5261@vader> (raw)
In-Reply-To: <87eggxzioj.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
On Wed, Oct 14, 2015 at 03=25=00PM +0200, Markus Armbruster wrote:
> Andrew Jones <drjones@redhat.com> writes:
>
> > On Wed, Oct 14, 2015 at 11:03:37AM +0200, Eduardo Otubo wrote:
> >> On Tue, Sep 29, 2015 at 11=39=46AM +0200, Eduardo Otubo wrote:
> >> > On Thu, Sep 24, 2015 at 03=50=04PM +0200, Andrew Jones wrote:
> >> > > On Thu, Sep 24, 2015 at 11:31:19AM +0200, Eduardo Otubo wrote:
> >> > > > On Wed, Jul 01, 2015 at 09=12=33AM -0400, Andrew Jones wrote:
> [...]
> >> > > > > diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> >> > > > > index f9de0d3390feb..33644a4e3c3d3 100644
> >> > > > > --- a/qemu-seccomp.c
> >> > > > > +++ b/qemu-seccomp.c
> >> > > > > @@ -237,7 +237,8 @@ static const struct QemuSeccompSyscall seccomp_whitelist[] = {
> >> > > > > { SCMP_SYS(fadvise64), 240 },
> >> > > > > { SCMP_SYS(inotify_init1), 240 },
> >> > > > > { SCMP_SYS(inotify_add_watch), 240 },
> >> > > > > - { SCMP_SYS(mbind), 240 }
> >> > > > > + { SCMP_SYS(mbind), 240 },
> >> > > > > + { SCMP_SYS(cacheflush), 240 },
> >>
> >> FYI: I had to fixed this minor mistake (using comma at the end of the
> >> list) before applying your patch.
> >
> > Does that violate a QEMU coding style? Because I actually put it there
> > on purpose so the next addition wouldn't have to modify the line (by
> > adding a comma), making git-blame more difficult to use.
>
> We have trailing commas all over the place, for precisely the reason you
> gave. I recommend to put it right back.
>
Well, that makes a lot of sense. I'll just put it back again and send
the pull request once more.
ps.: I just thought the guideline said to make sure every commit should
be "compilable" with no errors, perhaps I saw it somewhere else. Sorry
for the trouble.
--
Eduardo Otubo
ProfitBricks GmbH
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-14 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 13:12 [Qemu-devel] [PATCH] libseccomp: add cacheflush to whitelist Andrew Jones
2015-09-24 9:31 ` Eduardo Otubo
2015-09-24 13:50 ` Andrew Jones
2015-09-24 13:58 ` Peter Maydell
2015-09-29 9:39 ` Eduardo Otubo
2015-10-14 9:03 ` Eduardo Otubo
2015-10-14 12:41 ` Andrew Jones
2015-10-14 13:25 ` Markus Armbruster
2015-10-14 14:58 ` Eduardo Otubo [this message]
2015-10-14 15:14 ` Andrew Jones
2015-10-14 16:09 ` Markus Armbruster
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=20151014145813.GA5261@vader \
--to=eduardo.otubo@profitbricks.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmoore@redhat.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).