From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 23CC3C43219 for ; Sun, 28 Apr 2019 15:19:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E5458204FD for ; Sun, 28 Apr 2019 15:19:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tkP/p8tg" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726842AbfD1PTm (ORCPT ); Sun, 28 Apr 2019 11:19:42 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:45867 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726741AbfD1PTm (ORCPT ); Sun, 28 Apr 2019 11:19:42 -0400 Received: by mail-pg1-f193.google.com with SMTP id i21so498497pgi.12 for ; Sun, 28 Apr 2019 08:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=vNBqlYrmMjbbjO3oHtbD//+/sFNxxexbrdA2S/uRE68=; b=tkP/p8tgQQZEnDR+xo6yr2jdO4uFovLE3v/wjcCIeIt5kZ78hapVoN79YZNXk8z9xt Cmd9x9iA31SFiVKAtjgj0gv5f7P4awYYme1SOcqlX6e7hPl3pJVqmreHuSKZz3EdMo6v vqVcswbvnBqL1v31LXmtFssh0YEj09WlJ4HojFheh5U2GmMacwlhYp+lK+sUrXdXeHWD auAkMlJ+0lIjWyzOplgRBv5uM34Pyc8UbBxAD56WfavDt0mlmSe9Imy184hPbSHmP1Bw BrWnFmKduWRs8/Ijj820yYHXbFlX33ER8G4V8VhLuQVP/PIxtV7DjR/JjLi6J3XvZcz/ 97SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=vNBqlYrmMjbbjO3oHtbD//+/sFNxxexbrdA2S/uRE68=; b=rbc8x0B2zV0SJW/weOk0+o8037LsIBFbOJoVkC/aKtwWGSmPRfuZwsTcZ6piDzOQnE CBs02+bhZeDrt3PxhpGN4L/JKj3oRcDh7PGyVXl5t91KRKPAoQJ1zt+xtwSHKN9VIVbg cXiVo1A2kedsb16MkoPbyWasveQlpYxCrXNBka8uZ7CfhidxTP+vjQdhLQAdpSUe2I+E gIsEbknIJi+M2flr0FXGdhfIWETHoRpmNSAE6I4OzRTrK0ek8yBOoRVM7qbVS7QbWH1A stuoDbRWm5Wm/mEbxQBkoSUoAAKeEtBREi7pCqi66OKR5iwVrL4pcQliYZD0ElD+qVWi FPKQ== X-Gm-Message-State: APjAAAW80vkbYzFC3yRTjG3Nj/EtAffpkU83Piox3MAZVZoikQeDP/Nf zsc5aRiCqqR2FUwm4ju6Dq4= X-Google-Smtp-Source: APXvYqzIGzCAdnIcUO5SddXywdQVnG7EvoQoFWlidCokfH9H/piJpNLvCgo86D3eMiUMN/6XanIKZQ== X-Received: by 2002:a65:5cc8:: with SMTP id b8mr52290173pgt.36.1556464781873; Sun, 28 Apr 2019 08:19:41 -0700 (PDT) Received: from localhost (c-73-222-71-142.hsd1.ca.comcast.net. [73.222.71.142]) by smtp.gmail.com with ESMTPSA id g3sm9005384pfm.167.2019.04.28.08.19.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 28 Apr 2019 08:19:40 -0700 (PDT) Date: Sun, 28 Apr 2019 08:19:38 -0700 From: Richard Cochran To: Stephen Mallon Cc: "David S. Miller" , netdev@vger.kernel.org Subject: Re: [PATCH net] ipv4: Fix updating SOF_TIMESTAMPING_OPT_ID when SKBTX_HW_TSTAMP is enabled Message-ID: <20190428151938.njy3ip5szwj3vkda@localhost> References: <20190428054521.GA14504@stephen-mallon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190428054521.GA14504@stephen-mallon> User-Agent: NeoMutt/20170113 (1.7.2) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sun, Apr 28, 2019 at 03:45:21PM +1000, Stephen Mallon wrote: > Ensure that the unique timestamp identifier is incremented for skb hardware > timestamps, not just software timestamps. Thanks for fixing this. It has been at the back of my mind for a long time, but since I don't use this feature... oh well. This patch would be a candidate for stable kernels. Can you please add a Fixes: tag? Thanks, Richard