On Sun, Nov 01, 2015 at 04:08:27PM -0800, Hugh Dickins wrote: > On Fri, 30 Oct 2015, Minchan Kim wrote: > > From: Chen Gang <[email protected]> > > > > For uapi, need try to let all macros have same value, and MADV_FREE is > > added into main branch recently, so need redefine MADV_FREE for it. > > > > At present, '8' can be shared with all architectures, so redefine it to > > '8'. > > > > Cc: [email protected] <[email protected]>, > > Cc: [email protected] <[email protected]> > > Cc: [email protected] <[email protected]> > > Cc: Ralf Baechle <[email protected]> > > Cc: [email protected] <[email protected]> > > Cc: [email protected] <[email protected]> > > Cc: [email protected] <[email protected]> > > Cc: [email protected] <[email protected]> > > Cc: Arnd Bergmann <[email protected]> > > Cc: [email protected] > > Cc: [email protected] > > Acked-by: Minchan Kim <[email protected]> > > Signed-off-by: Chen Gang <[email protected]> > > Let me add > Acked-by: Hugh Dickins <[email protected]> > to this one too. > > But I have extended your mail's Cc list: Darrick pointed out earlier > that dietlibc has a Solaris #define MADV_FREE 0x5 in its mman.h, > and that was in the kernel's sparc mman.h up until 2.6.25. I doubt > that presents any obstacle nowadays, but Dave Miller should be Cc'ed. > > I was a little suspicious that 8 is available for MADV_FREE: why did > the common/generic parameters start at 9 instead of 8 back in 2.6.16? > I think the answer is that we had MADV_REMOVE coming in from one > direction, and MADV_DONTFORK coming from another direction, and when > Roland looked for where to start the commons for MADV_DONTFORK, it > appeared that 8 was occupied - by MADV_REMOVE; then a little later > MADV_REMOVE was shifted to become the first of the commons, at 9.
Thanks for Ack, Ccing relevant people and history! -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
