From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753149AbcIORsp (ORCPT ); Thu, 15 Sep 2016 13:48:45 -0400 Received: from mail-oi0-f44.google.com ([209.85.218.44]:35624 "EHLO mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752622AbcIORsi (ORCPT ); Thu, 15 Sep 2016 13:48:38 -0400 MIME-Version: 1.0 In-Reply-To: References: From: John Stultz Date: Thu, 15 Sep 2016 10:48:36 -0700 Message-ID: Subject: Re: [PATCH v3) posix-timers: make it configurable To: Nicolas Pitre Cc: Thomas Gleixner , Josh Triplett , Richard Cochran , lkml Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 14, 2016 at 8:47 PM, Nicolas Pitre wrote: > Many embedded systems typically don't need them. This removes about > 22KB from the kernel binary size on ARM when configured out. > > Corresponding syscalls are routed to a stub logging the attempt to > use those syscalls which should be enough of a clue if they were > disabled without proper consideration. They are: timer_create, > timer_gettime: timer_getoverrun, timer_settime, timer_delete, > clock_adjtime. > > The clock_settime, clock_gettime, clock_getres and clock_nanosleep syscalls > are replaced by simple wrappers compatible with CLOCK_REALTIME, > CLOCK_MONOTONIC and CLOCK_BOOTTIME only. Thanks for re-sending. I'm happier that you're keeping some basic functionality here. No real objections at this point. I need to apply it for testing and take a closer look, but its on my to-queue list. However, with an upcoming conference, as being a little later in the cycle I can't promise it will make it for the 4.9 merge window. But we'll see. thanks! -john