From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Bharat Bhushan <bharat.bhushan@nxp.com>,
Ruxandra Ioana Radulescu <ruxandra.radulescu@nxp.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"stuyoder@gmail.com" <stuyoder@gmail.com>,
Roy Pledge <roy.pledge@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
Bogdan Purcareata <bogdan.purcareata@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] staging: fsl-mc: use 32bits to support 64K size mc-portals
Date: Fri, 24 Nov 2017 16:58:48 +0100 [thread overview]
Message-ID: <20171124155848.GA8630@kroah.com> (raw)
In-Reply-To: <5A155642.70809@nxp.com>
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@nxp.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
next prev parent reply other threads:[~2017-11-24 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 7:48 [PATCH v3] staging: fsl-mc: use 32bits to support 64K size mc-portals Bharat Bhushan
2017-11-22 10:49 ` Laurentiu Tudor
2017-11-24 15:58 ` gregkh [this message]
2017-11-24 16:00 ` Bharat Bhushan
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=20171124155848.GA8630@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bharat.bhushan@nxp.com \
--cc=bogdan.purcareata@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuyoder@gmail.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