public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manjeet Pawar <manjeet.p@samsung.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	AKHILESH KUMAR <akhilesh.k@samsung.com>,
	Rohit Thapliyal <r.thapliyal@samsung.com>,
	PANKAJ MISHRA <pankaj.m@samsung.com>
Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ
Date: Fri, 09 Oct 2015 08:17:37 +0000 (GMT)	[thread overview]
Message-ID: <134741266.796671444378655653.JavaMail.weblogic@epmlwas03a> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=windows-1252, Size: 704 bytes --]

  
>> This looks correct now. A few more points though:
>> 
>> * My first thought would have been to do this by first defining the
>>   two symbols before the #include, and then adding an #ifdef in
>>   the generic file. Both approaches work though, any other opinions
>>   on this?

>That's what I was thinking as well. Maybe with a single #ifndef
>MINSIGSTKSZ to cover both macros.

I am sharing another patch which adds both macro in arm64/.../signal.h with new values and put a check with #ifndef in uapi/.../signal.h.
       
  
         
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

             reply	other threads:[~2015-10-09  8:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  8:17 Manjeet Pawar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-06  5:35 [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ Manjeet Pawar
2015-10-06  7:49 ` Arnd Bergmann
2015-10-06  9:37   ` Catalin Marinas
2015-10-06 10:31   ` Dave Martin
2015-10-06 10:51     ` Arnd Bergmann
2015-10-06 10:59       ` Andreas Schwab
2015-10-06 11:33         ` Dave Martin
2015-10-06 11:52           ` Andreas Schwab
2015-10-06 12:49             ` Dave Martin
2015-10-06 11:22       ` Dave Martin
2015-10-09  8:41       ` Arnd Bergmann
2015-10-12 13:53         ` Dave Martin
2015-10-06 10:19 ` Will Deacon

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=134741266.796671444378655653.JavaMail.weblogic@epmlwas03a \
    --to=manjeet.p@samsung.com \
    --cc=akhilesh.k@samsung.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.m@samsung.com \
    --cc=r.thapliyal@samsung.com \
    --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