From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: linux-headers-5.2 and proper use of SIOCGSTAMP Date: Sat, 20 Jul 2019 20:50:23 +0200 Message-ID: References: <20190720174844.4b989d34@sf> <87wogca86l.fsf@mid.deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <87wogca86l.fsf@mid.deneb.enyo.de> To: Florian Weimer Cc: Sergei Trofimovich , Networking , Linux Kernel Mailing List , GNU C Library , "David S. Miller" , Michael Kerrisk , linux-man List-Id: linux-man@vger.kernel.org On Sat, Jul 20, 2019 at 8:10 PM Florian Weimer wrote: > > * Sergei Trofimovich: > > > Should #include always be included by user app? > > Or should glibc tweak it's definition of '#include ' > > to make it available on both old and new version of linux headers? > > What is the reason for dropping SIOCGSTAMP from ? > > If we know that, it will be much easier to decide what to do about > . As far as I can tell, nobody thought it would be a problem to move it from asm/sockios.h to linux/sockios.h, as the general rule is that one should use the linux/*.h version if both exist, and that the asm/*.h version only contains architecture specific definitions. The new definition is the same across all architectures, so it made sense to have it in the common file. If the assumption was wrong, the obvious solution is to duplicate the definitions everywhere or move the common parts into asm-generic/sockios.h, but it would have been better to hear about that earlier. Arnd