From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935714AbdGTJJd (ORCPT ); Thu, 20 Jul 2017 05:09:33 -0400 Received: from mga02.intel.com ([134.134.136.20]:61782 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934006AbdGTJJb (ORCPT ); Thu, 20 Jul 2017 05:09:31 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,383,1496127600"; d="scan'208";a="1197550359" Message-ID: <1500541753.29303.129.camel@linux.intel.com> Subject: Re: uuid updates for 4.13-rc From: Andy Shevchenko To: Christoph Hellwig , Amir Goldstein , Andreas Noever , Michael Jamet , Mika Westerberg , Yehezkel Bernat Cc: linux-kernel@vger.kernel.org Date: Thu, 20 Jul 2017 12:09:13 +0300 In-Reply-To: <20170720075624.25619-1-hch@lst.de> References: <20170720075624.25619-1-hch@lst.de> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-07-20 at 09:56 +0200, Christoph Hellwig wrote: > Hi all, > > this series removes fixes a bug in the previous uuid pull request and > removes the the uuid_be type.  I had planned to send the > last patch for -rc1 already but held off to avoid merge conflicts > in linux-next. > > In the meantime the thunderbolt code added a few new instances, so > patch once removes them.  I'd like to get this small series into > 4.13-rc so that 4.13 is released without the uuid_be type. All patches in this series looks reasonable to me (1 is obvious bug fix, 2 is what we discussed with Mika, 3 obvious outcome). Reviewed-by: Andy Shevchenko I have sent uuid_le clean up, it looks I need to rebase it on top of this series. Though I'm still waiting for comments, tags there... -- Andy Shevchenko Intel Finland Oy