All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] libdecnumber: Fix warnings from smatch (missing static, boolean operations)
Date: Sun, 24 Aug 2014 13:21:10 +0400	[thread overview]
Message-ID: <53F9AE86.7040700@msgid.tls.msk.ru> (raw)
In-Reply-To: <1408525330-25414-1-git-send-email-sw@weilnetz.de>

Applied to -trivial, thank you!

But I've a small concern - should we really do this on "external" sources,
and divirge from upstream needlessly?

Thanks,

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] libdecnumber: Fix warnings from smatch (missing static, boolean operations)
Date: Sun, 24 Aug 2014 13:21:10 +0400	[thread overview]
Message-ID: <53F9AE86.7040700@msgid.tls.msk.ru> (raw)
In-Reply-To: <1408525330-25414-1-git-send-email-sw@weilnetz.de>

Applied to -trivial, thank you!

But I've a small concern - should we really do this on "external" sources,
and divirge from upstream needlessly?

Thanks,

/mjt

  reply	other threads:[~2014-08-24  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  9:02 [Qemu-trivial] [PATCH] libdecnumber: Fix warnings from smatch (missing static, boolean operations) Stefan Weil
2014-08-20  9:02 ` [Qemu-devel] " Stefan Weil
2014-08-24  9:21 ` Michael Tokarev [this message]
2014-08-24  9:21   ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-08-24  9:42   ` Stefan Weil
2014-08-24  9:42     ` [Qemu-devel] " Stefan Weil
2014-08-25  7:40     ` [Qemu-trivial] [Qemu-devel] " Markus Armbruster
2014-08-25  7:40       ` [Qemu-devel] [Qemu-trivial] " Markus Armbruster
2014-08-25 13:49     ` [Qemu-trivial] [Qemu-devel] " Tom Musta
2014-08-25 13:49       ` [Qemu-devel] [Qemu-trivial] " Tom Musta

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=53F9AE86.7040700@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.