From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: cns3xxx: pci: avoid potential stack overflow
Date: Thu, 08 Oct 2015 16:38:31 +0200 [thread overview]
Message-ID: <6292196.7OZzGKz28l@wuerfel> (raw)
In-Reply-To: <m3vbahy8wp.fsf@t19.piap.pl>
On Thursday 08 October 2015 12:03:18 Krzysztof Ha?asa wrote:
> Hi,
>
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > With those two changes in place, we no longer need the fake
> > pci_sys_data/pci_bus structures for faking config space writes,
> > and the stack usage goes down as well.
>
> > arch/arm/mach-cns3xxx/pcie.c | 71 +++++++++++++++++++++++++++++----------------------------------------
>
> I'm ATM unable to test this change, but will do that at some point.
> Meanwhile, I guess there is nothing I can say against this patch.
> Thanks.
>
> Acked-by: Krzysztof Ha?asa <khalasa@piap.pl>
>
Thanks! I've queued it up in next/fixes-non-critical for linux-4.4
now, if you find something wrong later, we can revert or fix up.
There is no urgency for this one, especially since you still want to
test it, so no reason to put it in 4.3.
This was the last pre-2015 build warning for the ARM defconfigs
and allmodconfig, all remaining warnings are regressions or new
code, and I've submitted patches for those. Let's see if we can
get to a warning-free kernel build in 4.4.
Arnd
prev parent reply other threads:[~2015-10-08 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 15:14 [PATCH] ARM: cns3xxx: pci: avoid potential stack overflow Arnd Bergmann
2015-05-27 6:45 ` Krzysztof Hałasa
2015-10-07 20:01 ` Arnd Bergmann
2015-10-07 20:05 ` [PATCH v2] " Arnd Bergmann
2015-10-08 10:03 ` Krzysztof Hałasa
2015-10-08 14:38 ` Arnd Bergmann [this message]
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=6292196.7OZzGKz28l@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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