From: Peter Zijlstra <peterz@infradead.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"geert@linux-m68k.org" <geert@linux-m68k.org>
Subject: Re: [PATCH v3] devres: Explicitly align datai[] to 64-bit
Date: Mon, 9 Jul 2018 17:14:47 +0200 [thread overview]
Message-ID: <20180709151447.GW2476@hirez.programming.kicks-ass.net> (raw)
Message-ID: <20180709151447.9INF1kxtibqgl1EnILQsxKoLcM6asv5y4AL5DznwqRM@z> (raw)
In-Reply-To: <dd7f96e4b08644769865adb302eb7d53@AcuMS.aculab.com>
On Mon, Jul 09, 2018 at 03:02:08PM +0000, David Laight wrote:
> Mostly related to the fpu - probably including the fpu save area.
So for the FPU save area in particular I know we play some horrific
games. As to the rest I really dont know.
I wouldn't mind it being changed, but from a cursory look, I couldn't
see it being anything other than 4 for x86_32.
next prev parent reply other threads:[~2018-07-09 15:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 13:45 [PATCH v3] devres: Explicitly align datai[] to 64-bit Alexey Brodkin
2018-07-09 13:45 ` Alexey Brodkin
2018-07-09 13:54 ` Peter Zijlstra
2018-07-09 13:54 ` Peter Zijlstra
2018-07-09 14:04 ` Mark Rutland
2018-07-09 14:04 ` Mark Rutland
2018-07-09 14:10 ` Geert Uytterhoeven
2018-07-09 14:10 ` Geert Uytterhoeven
2018-07-09 14:07 ` Alexey Brodkin
2018-07-09 14:07 ` Alexey Brodkin
2018-07-09 14:07 ` Peter Zijlstra
2018-07-09 14:07 ` Peter Zijlstra
2018-07-09 14:10 ` Peter Zijlstra
2018-07-09 14:10 ` Peter Zijlstra
2018-07-09 14:33 ` Alexey Brodkin
2018-07-09 14:33 ` Alexey Brodkin
2018-07-09 14:49 ` Peter Zijlstra
2018-07-09 14:49 ` Peter Zijlstra
2018-07-09 14:53 ` Alexey Brodkin
2018-07-09 14:53 ` Alexey Brodkin
2018-10-04 16:19 ` Alexey Brodkin
2018-10-04 16:19 ` Alexey Brodkin
2018-07-09 15:02 ` David Laight
2018-07-09 15:02 ` David Laight
2018-07-09 15:14 ` Peter Zijlstra [this message]
2018-07-09 15:14 ` Peter Zijlstra
2018-07-09 15:29 ` Mark Rutland
2018-07-09 15:29 ` Mark Rutland
2018-07-09 15:34 ` Peter Zijlstra
2018-07-09 15:34 ` Peter Zijlstra
2018-07-09 15:45 ` Peter Zijlstra
2018-07-09 15:45 ` Peter Zijlstra
2018-07-09 15:48 ` Mark Rutland
2018-07-09 15:48 ` Mark Rutland
2018-07-09 16:10 ` David Laight
2018-07-09 16:10 ` David Laight
2018-07-09 20:28 ` Vineet Gupta
2018-07-09 20:28 ` Vineet Gupta
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=20180709151447.GW2476@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=David.Laight@ACULAB.COM \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).