From owner-freebsd-current@freebsd.org Thu Jan 14 00:06:58 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6AF3EA81EA6 for ; Thu, 14 Jan 2016 00:06:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 38B921539; Thu, 14 Jan 2016 00:06:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x235.google.com with SMTP id 77so404949552ioc.2; Wed, 13 Jan 2016 16:06:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5yPrRCJQMHLTJMrZGTDriq0m+Jajpgoj5oTvGlZyrUs=; b=OC8HC2VYFx3Qvk1OieGHI09OUpgk7OvkORIzv1zxKEWskQgKJhPVZ9xw/h+L5gMY1q Cygn/Lp+NN/ynF+ErgXpjge0VumGaDV15qmh5ekxh3/jsQWEquiZRg6c+S/E/1W41rtU gzEaLbMUvdZNtI+LAu30+ZkAhu4PghEh+u7LjboVXJMWdpew2cn1FRFboJJwZBC1KNQv EL7k966xYW0uo+aH8seV4S/qCIDmUVnEy109E8/IM8zYV6LTPjrvUnTUwLKHqTvptPqK wNTY8b6jSAVqYfCbOJo2motMGb/b6DgZekIqLbNVlAdwr6Nya0KS+cHXdeGXGA2p8xAm Kl3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=5yPrRCJQMHLTJMrZGTDriq0m+Jajpgoj5oTvGlZyrUs=; b=asoGzbPS8PqWS/n8Tj75b9jLlVCP2fwOp7WIOqXoRuVFG23TUgXxdFMiPBq/tvQL7b 0pCljWRfAdKvbJQWNta/4NqNf/eNETltrhiiopD60MfC4Y7UyWuTXwHLO7DhSxYPq1Za uOxs7SOTiVXZKy+MlnAAZs/EVgPEDc7IamXZCEdZtPf896W3SGpBx0MTgWMoEET50lj7 sYb71yKwR2xUwdpgX5F3qxeMHbuTHgpaG1KlFCiJ1Fjrx53JBnS9qzmq9+PEJ7UbrEIW xIb021N+Ozl1O2alQ74IQthMUcGjhQVgSsE4//C17Lg4QOUr7kisWiN6MYdI6CgK1WM7 jTpw== X-Gm-Message-State: ALoCoQkLPD0SborRzs6eV+0aKUdi6KiccXeABawFvslu43uzIs94FHatRXOQ3tjPjjGcEDjerRUL5bGbC2Iwr4YMITSbVWGB9Q== MIME-Version: 1.0 X-Received: by 10.107.162.146 with SMTP id l140mr1612396ioe.123.1452730017626; Wed, 13 Jan 2016 16:06:57 -0800 (PST) Received: by 10.36.121.202 with HTTP; Wed, 13 Jan 2016 16:06:57 -0800 (PST) In-Reply-To: <5696E5DF.7080202@freebsd.org> References: <5696E5DF.7080202@freebsd.org> Date: Wed, 13 Jan 2016 16:06:57 -0800 Message-ID: Subject: Re: MFC question From: Adrian Chadd To: Allan Jude Cc: freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2016 00:06:58 -0000 why can't you provide both in stable/10 ? -a On 13 January 2016 at 16:03, Allan Jude wrote: > I was considering MFC'ing this commit to stable/10: > > https://svnweb.freebsd.org/base?view=revision&revision=292782 > > It replaces the kernel implementation of SHA512 (sys/crypto/sha2/sha2.c) > with cperciva@'s version from libmd. In benchmarks it was 5-30% faster, > on x86_64 and arm/mips. > > But, in head I ended up being asked to bump __FreeBSD_version because it > removes sys/crypto/sha2.h which was apparently used by a 3rd party > driver, and replaces it with sys/crypto/sha512.h > > Does this kind of change mean it cannot be MFCd to stable/10? Or is it > ok to MFC it? > > -- > Allan Jude > > >