[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171124155848.GA8630@kroah.com>
Date: Fri, 24 Nov 2017 16:58:48 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@....com>
Cc: Bharat Bhushan <bharat.bhushan@....com>,
Ruxandra Ioana Radulescu <ruxandra.radulescu@....com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"stuyoder@...il.com" <stuyoder@...il.com>,
Roy Pledge <roy.pledge@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Leo Li <leoyang.li@....com>,
Bogdan Purcareata <bogdan.purcareata@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3] staging: fsl-mc: use 32bits to support 64K size
mc-portals
On Wed, Nov 22, 2017 at 10:49:50AM +0000, Laurentiu Tudor wrote:
>
>
> On 11/22/2017 09:48 AM, Bharat Bhushan wrote:
> > As per APIs each mc-portal is of 64K size while currently
> > 16bits (type u16) is used to store size of mc-portal.
> > In these cases upper bit of portal size gets truncated.
> >
> > Signed-off-by: Bharat Bhushan <Bharat.Bhushan@....com>
> > ---
>
> Ok, so just to clarify this fixes the case where size is equal (or maybe
> larger in the future) to 0x10000.
Is this something that can happen today? Is this needed in 4.14 to fix
a problem people are having and need to be backported to stable, or can
it wait until 4.15?
thanks,
greg k-h
Powered by blists - more mailing lists