From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from vps0.lunn.ch (vps0.lunn.ch. [178.209.37.122]) by gmr-mx.google.com with ESMTPS id d22si436051wmd.0.2016.12.08.09.29.25 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Thu, 08 Dec 2016 09:29:25 -0800 (PST) Date: Thu, 8 Dec 2016 18:29:23 +0100 From: Andrew Lunn To: Gregory CLEMENT Cc: Alessandro Zummo , Alexandre Belloni , rtc-linux@googlegroups.com, Jason Cooper , Sebastian Hesselbarth , Thomas Petazzoni , linux-arm-kernel@lists.infradead.org, Shaker Daibes Subject: [rtc-linux] Re: [PATCH 1/3] rtc: armada38x: improve RTC errata implementation Message-ID: <20161208172923.GQ26852@lunn.ch> References: <20161208171010.29446-1-gregory.clement@free-electrons.com> <20161208171010.29446-2-gregory.clement@free-electrons.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 In-Reply-To: <20161208171010.29446-2-gregory.clement@free-electrons.com> Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , > +struct str_value_to_freq { > + unsigned long value; > + u8 freq; > +} __packed; > + > +static unsigned long read_rtc_register_wa(struct armada38x_rtc *rtc, u8 rtc_reg) > +{ > + unsigned long value_array[SAMPLE_NR], i, j, value; > + unsigned long max = 0, index_max = SAMPLE_NR - 1; > + struct str_value_to_freq value_to_freq[SAMPLE_NR]; Hi Gregory This appears to be putting over 900 bytes on the stack. Is there any danger of overflowing the stack? Would it be safer to make these arrays part of armada38x_rtc? Andrew -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrew@lunn.ch (Andrew Lunn) Date: Thu, 8 Dec 2016 18:29:23 +0100 Subject: [PATCH 1/3] rtc: armada38x: improve RTC errata implementation In-Reply-To: <20161208171010.29446-2-gregory.clement@free-electrons.com> References: <20161208171010.29446-1-gregory.clement@free-electrons.com> <20161208171010.29446-2-gregory.clement@free-electrons.com> Message-ID: <20161208172923.GQ26852@lunn.ch> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > +struct str_value_to_freq { > + unsigned long value; > + u8 freq; > +} __packed; > + > +static unsigned long read_rtc_register_wa(struct armada38x_rtc *rtc, u8 rtc_reg) > +{ > + unsigned long value_array[SAMPLE_NR], i, j, value; > + unsigned long max = 0, index_max = SAMPLE_NR - 1; > + struct str_value_to_freq value_to_freq[SAMPLE_NR]; Hi Gregory This appears to be putting over 900 bytes on the stack. Is there any danger of overflowing the stack? Would it be safer to make these arrays part of armada38x_rtc? Andrew