All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Kim Phillips <kim.phillips@freescale.com>,
	kernel-janitors@vger.kernel.org,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/ipic: Fix a bounds check in ipic_set_priority()
Date: Thu, 06 Dec 2018 09:34:20 +0000	[thread overview]
Message-ID: <20181206093420.GL3073@unbuntlaptop> (raw)
In-Reply-To: <87sgzchcw8.fsf@concordia.ellerman.id.au>

On Wed, Dec 05, 2018 at 02:26:47PM +1100, Michael Ellerman wrote:
> Can smatch help us find things like this that are defined non-static but
> never used?
> 

It's too tricky because it depends on the .config as well.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Kim Phillips <kim.phillips@freescale.com>,
	kernel-janitors@vger.kernel.org,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/ipic: Fix a bounds check in ipic_set_priority()
Date: Thu, 6 Dec 2018 12:34:20 +0300	[thread overview]
Message-ID: <20181206093420.GL3073@unbuntlaptop> (raw)
In-Reply-To: <87sgzchcw8.fsf@concordia.ellerman.id.au>

On Wed, Dec 05, 2018 at 02:26:47PM +1100, Michael Ellerman wrote:
> Can smatch help us find things like this that are defined non-static but
> never used?
> 

It's too tricky because it depends on the .config as well.

regards,
dan carpenter

  parent reply	other threads:[~2018-12-06  9:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 14:48 [PATCH] powerpc/ipic: Fix a bounds check in ipic_set_priority() Dan Carpenter
2018-12-03 14:48 ` Dan Carpenter
2018-12-05  3:26 ` Michael Ellerman
2018-12-05  3:26   ` Michael Ellerman
2018-12-05  8:11   ` Julia Lawall
2018-12-05  8:11     ` Julia Lawall
2018-12-05 12:04     ` Michael Ellerman
2018-12-05 12:04       ` Michael Ellerman
2018-12-05 12:06       ` Julia Lawall
2018-12-05 12:06         ` Julia Lawall
2018-12-06  7:18   ` Christophe LEROY
2018-12-06  7:18     ` Christophe LEROY
2018-12-06  8:12     ` Julia Lawall
2018-12-06  8:12       ` Julia Lawall
2018-12-11 14:26       ` Dan Carpenter
2018-12-11 14:26         ` Dan Carpenter
2018-12-07  2:07     ` Michael Ellerman
2018-12-07  2:07       ` Michael Ellerman
2018-12-10 12:05       ` Christophe Leroy
2018-12-10 12:05         ` Christophe Leroy
2018-12-06  9:34   ` Dan Carpenter [this message]
2018-12-06  9:34     ` Dan Carpenter

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=20181206093420.GL3073@unbuntlaptop \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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.