From owner-svn-src-stable@freebsd.org Fri May 11 23:31:48 2018 Return-Path: Delivered-To: svn-src-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F500FD42D5; Fri, 11 May 2018 23:31:48 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F040B732DE; Fri, 11 May 2018 23:31:47 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-wm0-f54.google.com with SMTP id x12-v6so4555657wmc.0; Fri, 11 May 2018 16:31:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7N5lC/K43JaJu9nz9g2seXAsGbunWbRNMCv08Oh7MIM=; b=majeALttW6f6FHHQSeHRrImn4nJm53eIgFN0OXv5FPJA5ni65lpxyeC15owJofZF+Y CzUowAwNJ6BOuQdQ8tOm4mxjPyEeAorF10Y3o6ezqk+cy6E7gLUnZImtXYiJgjswAAMg 9iPNgzZWv6rs3ND7toXn3oimCFeAgR2DilTQlTFC8w6lFCI1iLyKwx6mZoXn+jonhAP9 Ff6NqyxbmN12g9nd+DA8nJmIUCyevU9nASyT/faN9q9lUxL3Psw1fY6Rm31Wo1eWmd22 Le5weqPAbE8tnGPmcUPF+qmPK4KXeS9HvlVgatSetI9KA/cG1klc/SBm/UOES2ZRe/OH Wb+g== X-Gm-Message-State: ALKqPwf6TZVwB8Ujoixv6XTSK66Jwa2D4JqO2shMKdhPBau2Ee3A36rT 9pXJ6iOXdKS5tmnTcVHZ6sNiMLCM X-Google-Smtp-Source: AB8JxZrKNENKVGyJ5t5AGqNNpYTk2pbJCLfJXeakTpxPubz7R8IhSVqLZLrfGJxhUYoINSYLe63fqg== X-Received: by 2002:a50:8d59:: with SMTP id t25-v6mr783681edt.238.1526081501587; Fri, 11 May 2018 16:31:41 -0700 (PDT) Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com. [209.85.128.175]) by smtp.gmail.com with ESMTPSA id g7-v6sm2195628edf.90.2018.05.11.16.31.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 May 2018 16:31:41 -0700 (PDT) Received: by mail-wr0-f175.google.com with SMTP id 94-v6so6767832wrf.5; Fri, 11 May 2018 16:31:41 -0700 (PDT) X-Received: by 2002:adf:b583:: with SMTP id c3-v6mr651794wre.228.1526081501322; Fri, 11 May 2018 16:31:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.197.74 with HTTP; Fri, 11 May 2018 16:31:40 -0700 (PDT) In-Reply-To: <201805112040.w4BKeQvO053076@repo.freebsd.org> References: <201805112040.w4BKeQvO053076@repo.freebsd.org> From: "Jonathan T. Looney" Date: Fri, 11 May 2018 19:31:40 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: svn commit: r333503 - stable/11/sys/net To: Stephen Hurd Cc: src-committers , svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: svn-src-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for all the -stable branches of the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 23:31:48 -0000 On Fri, May 11, 2018 at 4:40 PM, Stephen Hurd wrote: > > Author: shurd > Date: Fri May 11 20:40:26 2018 > New Revision: 333503 > URL: https://svnweb.freebsd.org/changeset/base/333503 > > Log: > MFC r333329, r333366, r333373 > > r333329: Fix off-by-one error requesting tx interrupt > r333366: Cleanup queues when iflib_device_register fails > r333373: Log iflib_tx_structures_setup failure in function > Is this an acceptable style for MFC logs? I'm asking because I actually prefer this to reading (or compiling) the concatenated log messages from several changes. However, I never knew it was acceptable to summarize like this. If it is, I'd like to know so I can adopt it for run-of-the-mill MFCs. Jonathan