From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-kernel@vger.kernel.org,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [PATCH] [media] zl10353: use div_u64 instead of do_div
Date: Fri, 12 Feb 2016 22:45:34 +0100 [thread overview]
Message-ID: <5158925.0PEQLt1vYj@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1602121634040.13632@knanqh.ubzr>
On Friday 12 February 2016 16:38:53 Nicolas Pitre wrote:
> On Fri, 12 Feb 2016, Arnd Bergmann wrote:
>
> > On Friday 12 February 2016 13:21:33 Nicolas Pitre wrote:
> > > This is all related to the gcc bug for which I produced a test case
> > > here:
> > >
> > > http://article.gmane.org/gmane.linux.kernel.cross-arch/29801
> > >
> > > Do you know if this is fixed in recent gcc?
> >
> > I have a fairly recent gcc, but I also never got around to submit
> > it properly.
> >
> > However, I did stumble over an older patch I did now, which I could
> > not remember what it was good for. It does fix the problem, and
> > it seems to be a better solution.
>
> WTF?
Even better, it also fixes this one:
drivers/mtd/chips/cfi_cmdset_0020.c: In function 'cfi_staa_write_buffers':
drivers/mtd/chips/cfi_cmdset_0020.c:651:1: error: the frame size of 1064 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
I have not even looked what that is, I only saw show up the other day.
Arnd
next prev parent reply other threads:[~2016-02-12 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 14:27 [PATCH] [media] zl10353: use div_u64 instead of do_div Arnd Bergmann
2016-02-12 16:32 ` Mauro Carvalho Chehab
2016-02-12 17:04 ` Arnd Bergmann
2016-02-12 18:21 ` Nicolas Pitre
2016-02-12 21:01 ` Arnd Bergmann
2016-02-12 21:38 ` Nicolas Pitre
2016-02-12 21:45 ` Arnd Bergmann [this message]
2016-02-13 8:39 ` Ard Biesheuvel
2016-02-13 21:57 ` Nicolas Pitre
2016-02-14 7:57 ` Ard Biesheuvel
2016-02-14 16:52 ` Nicolas Pitre
2016-02-14 19:06 ` Ard Biesheuvel
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=5158925.0PEQLt1vYj@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=nicolas.pitre@linaro.org \
--cc=stefanr@s5r6.in-berlin.de \
/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).