public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Rientjes <rientjes@google.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
	christophe.guerard@intel.com
Subject: Re: [PATCH 3/4] Intel PTI implementaiton of MIPI 1149.7.
Date: Wed, 20 Apr 2011 11:07:18 -0700	[thread overview]
Message-ID: <1303322838.13457.46.camel@localhost> (raw)
In-Reply-To: <20110420104654.6b457142@lxorguk.ukuu.org.uk>

On Wed, 2011-04-20 at 10:46 +0100, Alan Cox wrote:
> > is small enough that it shouldn't be an issue.  Otherwise there's nothing 
> > protecting sizeof(current->comm) from changing without holding 
> > task_lock(current).
> 
> The C language definition for one - sizeof() is a constant at compile time

K, thanks, I'll look at re-working these couple lines of code.



  reply	other threads:[~2011-04-20 18:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 22:58 [PATCH 3/4] Intel PTI implementaiton of MIPI 1149.7 james_p_freyensee
2011-04-19 23:15 ` Randy Dunlap
2011-04-20 23:05   ` J Freyensee
2011-04-20 23:10     ` Randy Dunlap
2011-04-21 21:06       ` J Freyensee
2011-04-21 21:17         ` Randy Dunlap
2011-04-20  1:25 ` David Rientjes
2011-04-20  9:46   ` Alan Cox
2011-04-20 18:07     ` J Freyensee [this message]
2011-04-22 17:57   ` J Freyensee
  -- strict thread matches above, loose matches on Subject: below --
2011-04-22 23:32 james_p_freyensee
2011-04-24  0:55 ` Jesper Juhl
2011-04-24  1:08   ` Jesper Juhl
2011-05-05 17:06     ` J Freyensee
2011-05-05 20:37       ` Jesper Juhl
2011-05-05 17:27   ` J Freyensee
2011-05-05 20:42     ` Jesper Juhl
2011-05-05 22:30     ` J Freyensee
2011-05-06 23:56 james_p_freyensee

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=1303322838.13457.46.camel@localhost \
    --to=james_p_freyensee@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=christophe.guerard@intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=suhail.ahmed@intel.com \
    /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