All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "Jon Medhurst (Tixy)"
	<tixy-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	"gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] decompressors: fix "no limit" output buffer length
Date: Mon, 22 Jul 2013 20:32:11 -0700	[thread overview]
Message-ID: <51EDF93B.1070101@wwwdotorg.org> (raw)
In-Reply-To: <51EDE724.5020507-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 07/22/2013 07:15 PM, Alex Courbot wrote:
...
> Although the patch seems ok to me in its current form, there are two
> points for which I still have small doubts:
> 
> 1) Whether size_t and pointers will have the same size on all platforms.

ptrsize_t?

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] decompressors: fix "no limit" output buffer length
Date: Mon, 22 Jul 2013 20:32:11 -0700	[thread overview]
Message-ID: <51EDF93B.1070101@wwwdotorg.org> (raw)
In-Reply-To: <51EDE724.5020507@nvidia.com>

On 07/22/2013 07:15 PM, Alex Courbot wrote:
...
> Although the patch seems ok to me in its current form, there are two
> points for which I still have small doubts:
> 
> 1) Whether size_t and pointers will have the same size on all platforms.

ptrsize_t?

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alex Courbot <acourbot@nvidia.com>
Cc: "Jon Medhurst (Tixy)" <tixy@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"gnurou@gmail.com" <gnurou@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] decompressors: fix "no limit" output buffer length
Date: Mon, 22 Jul 2013 20:32:11 -0700	[thread overview]
Message-ID: <51EDF93B.1070101@wwwdotorg.org> (raw)
In-Reply-To: <51EDE724.5020507@nvidia.com>

On 07/22/2013 07:15 PM, Alex Courbot wrote:
...
> Although the patch seems ok to me in its current form, there are two
> points for which I still have small doubts:
> 
> 1) Whether size_t and pointers will have the same size on all platforms.

ptrsize_t?

  parent reply	other threads:[~2013-07-23  3:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  6:56 [PATCH] decompressors: fix "no limit" output buffer length Alexandre Courbot
2013-07-22  6:56 ` Alexandre Courbot
2013-07-22 18:08 ` Jon Medhurst (Tixy)
2013-07-22 18:08   ` Jon Medhurst (Tixy)
2013-07-23  2:15   ` Alex Courbot
2013-07-23  2:15     ` Alex Courbot
     [not found]     ` <51EDE724.5020507-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-07-23  3:32       ` Stephen Warren [this message]
2013-07-23  3:32         ` Stephen Warren
2013-07-23  3:32         ` Stephen Warren
     [not found]         ` <51EDF93B.1070101-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-07-23  5:01           ` Alex Courbot
2013-07-23  5:01             ` Alex Courbot
2013-07-23  5:01             ` Alex Courbot

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=51EDF93B.1070101@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tixy-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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.