linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julien Thierry <julien.thierry@arm.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: David Binderman <dcb314@hotmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-4.20-rc1/arch/arm/vfp/vfpmodule.c:576: possible cut'n'paste error
Date: Tue, 6 Nov 2018 16:44:45 +0000	[thread overview]
Message-ID: <f03de303-041c-a183-40b8-6afc2a872af2@arm.com> (raw)
In-Reply-To: <20181106163959.GL30658@n2100.armlinux.org.uk>



On 06/11/18 16:39, Russell King - ARM Linux wrote:
> On Tue, Nov 06, 2018 at 04:29:54PM +0000, Julien Thierry wrote:
>> Hi Russel, David,
>>
>> On 06/11/18 16:20, Russell King - ARM Linux wrote:
>>> On Mon, Nov 05, 2018 at 01:53:13PM +0000, David Binderman wrote:
>>>> Hello there,
>>>>
>>>> 2nd try. Plain text might help.
>>>
>>> Yep, Linux kernel development generally doesn't like wasteful html
>>> emails, sorry.
>>>
>>>> linux-4.20-rc1/arch/arm/vfp/vfpmodule.c:576]: (warning) Redundant assignment of 'ufp_exc->fpinst2' to itself.
>>>>
>>>> Source code is
>>>>
>>>>         ufp_exc->fpexc = hwstate->fpexc;
>>>>         ufp_exc->fpinst = hwstate->fpinst;
>>>>         ufp_exc->fpinst2 = ufp_exc->fpinst2;
>>>
>>> Thanks for the report - it most certainly is a bug introduced by
>>> Julien's patches, but I don't get your warning here.  Which compiler
>>> produces that warning?
>>>
>>
>> Hmmm, silly typo/copy-paste from my end. Last line should be:
>>
>> 	ufp_exc->fpinst2 = hwstate->fpinst2;
>>
>> Sorry about that.
>>
>>> Julien - unfortunately, I've just asked Linus to take another fix
>>> for Spectre, so we're going to have to wait a bit before I can
>>> submit something for this.
>>>
>>
>> It is just a one line fix, should I submit a patch to the LAKML or patch
>> system?
> 
> Both I guess.
> 
>> Otherwise let me know when is it best for you to receive the fix then to
>> send to Linus.
> 
> As mentioned, I'll have to wait a while, it's not fair to send a pull
> request for one patch followed immediately by another pull request for
> another patch on top of the same pull request.
> 

Makes sense. I'll send the fix in a short time.

Thanks,

-- 
Julien Thierry

  reply	other threads:[~2018-11-06 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR08MB3342D4ADBFBC43F2BE2FD34D9CCA0@VI1PR08MB3342.eurprd08.prod.outlook.com>
     [not found] ` <VI1PR08MB33420789A2AA1096D3F5FC9D9CCA0@VI1PR08MB3342.eurprd08.prod.outlook.com>
2018-11-06 16:20   ` linux-4.20-rc1/arch/arm/vfp/vfpmodule.c:576: possible cut'n'paste error Russell King - ARM Linux
2018-11-06 16:29     ` Julien Thierry
2018-11-06 16:39       ` Russell King - ARM Linux
2018-11-06 16:44         ` Julien Thierry [this message]
     [not found]     ` <VI1PR08MB33427CD1C653245DBB979B9B9CCB0@VI1PR08MB3342.eurprd08.prod.outlook.com>
2018-11-06 16:37       ` Russell King - ARM Linux
2018-11-10 17:54         ` Robert Jarzmik

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=f03de303-041c-a183-40b8-6afc2a872af2@arm.com \
    --to=julien.thierry@arm.com \
    --cc=dcb314@hotmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).