LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Colin Ian King <colin.king@canonical.com>,
	John Johansen <john.johansen@canonical.com>,
	James Morris <jmorris@namei.org>,
	"Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] apparmor: secid: fix error return value in error handling path
Date: Tue, 15 May 2018 09:41:40 -0500	[thread overview]
Message-ID: <03eb44c5-ee46-f402-7ae9-5d11a233c1f8@embeddedor.com> (raw)
In-Reply-To: <1f4a965f-a245-a5a9-f815-9915df9b3a9d@canonical.com>

Hi Colin,


Sorry for the late response. I've been on the road for the last 12 days 
and I'm just back.

On 05/04/2018 09:36 AM, Colin Ian King wrote:
> Hi Gustavo,
> 
> if you are using the coverity scan bug tracking, please can you mark a
> bug as being worked on by yourself so I don't work on it at the same
> time as we're duplicating work here.
> 

Yeah, I've noticed that. I actually do that very often, and in some 
cases I've also noticed you have made changes to the same bug regardless 
of that.

The problem is that the Coverity dashboard doesn't refresh itself, so 
anyone using it should refresh it at all times in order to keep track of 
the bugs that have already been taken by somebody else.

So I think this kind of "collisions" will continue to happen unless 
people add the auto-refresh feature to the Coverity dashboard. :/

Thanks
--
Gustavo

      reply	other threads:[~2018-05-15 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 14:09 Gustavo A. R. Silva
2018-05-04 14:36 ` Colin Ian King
2018-05-15 14:41   ` Gustavo A. R. Silva [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=03eb44c5-ee46-f402-7ae9-5d11a233c1f8@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=colin.king@canonical.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --subject='Re: [PATCH v2] apparmor: secid: fix error return value in error handling path' \
    /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

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).