All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Frediano Ziglio <frediano.ziglio@citrix.com>
Cc: "konrad@kernel.org" <konrad@kernel.org>,
	"Keir (Xen.org)" <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"JBeulich@suse.com" <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 4/5] Check no constructor section
Date: Wed, 6 Feb 2013 16:04:48 +0000	[thread overview]
Message-ID: <51127F20.8010604@eu.citrix.com> (raw)
In-Reply-To: <7CE799CC0E4DE04B88D5FDF226E18AC201058D45836D@LONPMAILBOX01.citrite.net>

On 06/02/13 16:10, Frediano Ziglio wrote:
> On Wed, 2013-02-06 at 15:01 +0000, Jan Beulich wrote:
>>>>> On 06.02.13 at 15:32, Frediano Ziglio <frediano.ziglio@citrix.com> wrote:
>>> Safety check for initialization objects.
>>> Constructors are not used so check some module does not use them.
>> Once again - why?
>>
>> And repeating earlier complaints of mine - why do you continue to
>> re-post without having addressed all comments on prior revisions
>> (verbally or by changing the patches)? This is just wasting
>> reviewers' time.
>>
>> Jan
>>
> Nothing personal, I'm just a bad mail reader. In this case I checked
> mails filtering with "cover" but your reply didn't have it on the
> subject.

If that's going to be your modus operandi, then *you* need to put the 
search term in your subject line; for example, by making your one-line 
summary "cover: Check no constructor section"

  -George

  reply	other threads:[~2013-02-06 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 14:32 [PATCH v5] Coverage support Frediano Ziglio
2013-02-06 14:32 ` [PATCH 1/5] Call constructors during initialization Frediano Ziglio
2013-02-06 14:59   ` Jan Beulich
2013-02-06 14:32 ` [PATCH 2/5] Adding support for coverage information Frediano Ziglio
2013-02-06 14:32 ` [PATCH 3/5] Implement code to read coverage informations Frediano Ziglio
2013-02-06 17:12   ` Ian Campbell
2013-02-06 18:57     ` Frediano Ziglio
2013-02-06 14:32 ` [PATCH 4/5] Check no constructor section Frediano Ziglio
2013-02-06 15:01   ` Jan Beulich
2013-02-06 16:10     ` Frediano Ziglio
2013-02-06 16:04       ` George Dunlap [this message]
2013-02-06 14:33 ` [PATCH 5/5] Add small utility to deal with test coverage information from Xen Frediano Ziglio

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=51127F20.8010604@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=frediano.ziglio@citrix.com \
    --cc=keir@xen.org \
    --cc=konrad@kernel.org \
    --cc=xen-devel@lists.xen.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 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.