From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 651F421A16EFD for ; Thu, 18 May 2017 01:56:31 -0700 (PDT) Date: Thu, 18 May 2017 10:56:29 +0200 From: Christoph Hellwig Subject: Re: [PATCH 23/23] uuid: remove uuid_be Message-ID: <20170518085629.GA6149@lst.de> References: <20170518062705.25902-1-hch@lst.de> <20170518062705.25902-24-hch@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Amir Goldstein Cc: linux-xfs , linux-raid@vger.kernel.org, linux-nvdimm@lists.01.org, Mimi Zohar , Hugh Dickins , linux-kernel , Steven Whitehouse , David Howells , linux-fsdevel , Andy Shevchenko , Shaohua Li , Christoph Hellwig List-ID: On Thu, May 18, 2017 at 10:57:24AM +0300, Amir Goldstein wrote: > I reviewed the entire series. You may add > Reviewed-by: Amir Goldstein > > to any of the patches as you see fit. Thanks, done! > Now let's talk about how this is going to be merged. > Do you intend to send Linus a pull request? Yes, that might be the best idea. I'm also contemplating listing me plus anyone volunteering (you?, Andy) as maintaines for the uuid code. But first I'll need a few more reviews, at least for the XFS bits. > Get those patches merged via someone else's tree? > Is this branch listed for linux-next build? Not yet. > The reason I am asking is because this last removal patch should probably > be applied near the end of the merge window (?). > Because maintainers cannot apply patches with code that uses the new > uuid_t to linux-next branches and we don't want linux-next build to fail > with new code that uses uuid_be... Yeah, we can probably defer that one for now. > More to the point, I would like to re-post the patch > ("tmpfs: generate random sb->s_uuid") using uuid_gen() > instead of generate_random_uuid() as you proposed. > Hugh has already acked the intent "once fs is agreed on the way to go" > When and how would I have this patch applied? > Obvious solution.. can you apply this patch to your branch? Yes. > Do you need me to re-post it? Please do. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 23/23] uuid: remove uuid_be Date: Thu, 18 May 2017 10:56:29 +0200 Message-ID: <20170518085629.GA6149@lst.de> References: <20170518062705.25902-1-hch@lst.de> <20170518062705.25902-24-hch@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" To: Amir Goldstein Cc: linux-xfs , linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org, Mimi Zohar , Hugh Dickins , linux-kernel , Steven Whitehouse , David Howells , linux-fsdevel , Andy Shevchenko , Shaohua Li , Christoph Hellwig List-Id: linux-raid.ids On Thu, May 18, 2017 at 10:57:24AM +0300, Amir Goldstein wrote: > I reviewed the entire series. You may add > Reviewed-by: Amir Goldstein > > to any of the patches as you see fit. Thanks, done! > Now let's talk about how this is going to be merged. > Do you intend to send Linus a pull request? Yes, that might be the best idea. I'm also contemplating listing me plus anyone volunteering (you?, Andy) as maintaines for the uuid code. But first I'll need a few more reviews, at least for the XFS bits. > Get those patches merged via someone else's tree? > Is this branch listed for linux-next build? Not yet. > The reason I am asking is because this last removal patch should probably > be applied near the end of the merge window (?). > Because maintainers cannot apply patches with code that uses the new > uuid_t to linux-next branches and we don't want linux-next build to fail > with new code that uses uuid_be... Yeah, we can probably defer that one for now. > More to the point, I would like to re-post the patch > ("tmpfs: generate random sb->s_uuid") using uuid_gen() > instead of generate_random_uuid() as you proposed. > Hugh has already acked the intent "once fs is agreed on the way to go" > When and how would I have this patch applied? > Obvious solution.. can you apply this patch to your branch? Yes. > Do you need me to re-post it? Please do. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:57573 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751486AbdERI4b (ORCPT ); Thu, 18 May 2017 04:56:31 -0400 Date: Thu, 18 May 2017 10:56:29 +0200 From: Christoph Hellwig Subject: Re: [PATCH 23/23] uuid: remove uuid_be Message-ID: <20170518085629.GA6149@lst.de> References: <20170518062705.25902-1-hch@lst.de> <20170518062705.25902-24-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Amir Goldstein Cc: Christoph Hellwig , Andy Shevchenko , linux-fsdevel , Shaohua Li , Dan Williams , David Howells , Steven Whitehouse , Mimi Zohar , linux-xfs , linux-raid@vger.kernel.org, linux-nvdimm@lists.01.org, linux-kernel , Hugh Dickins On Thu, May 18, 2017 at 10:57:24AM +0300, Amir Goldstein wrote: > I reviewed the entire series. You may add > Reviewed-by: Amir Goldstein > > to any of the patches as you see fit. Thanks, done! > Now let's talk about how this is going to be merged. > Do you intend to send Linus a pull request? Yes, that might be the best idea. I'm also contemplating listing me plus anyone volunteering (you?, Andy) as maintaines for the uuid code. But first I'll need a few more reviews, at least for the XFS bits. > Get those patches merged via someone else's tree? > Is this branch listed for linux-next build? Not yet. > The reason I am asking is because this last removal patch should probably > be applied near the end of the merge window (?). > Because maintainers cannot apply patches with code that uses the new > uuid_t to linux-next branches and we don't want linux-next build to fail > with new code that uses uuid_be... Yeah, we can probably defer that one for now. > More to the point, I would like to re-post the patch > ("tmpfs: generate random sb->s_uuid") using uuid_gen() > instead of generate_random_uuid() as you proposed. > Hugh has already acked the intent "once fs is agreed on the way to go" > When and how would I have this patch applied? > Obvious solution.. can you apply this patch to your branch? Yes. > Do you need me to re-post it? Please do. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754899AbdERI4f (ORCPT ); Thu, 18 May 2017 04:56:35 -0400 Received: from verein.lst.de ([213.95.11.211]:57573 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751486AbdERI4b (ORCPT ); Thu, 18 May 2017 04:56:31 -0400 Date: Thu, 18 May 2017 10:56:29 +0200 From: Christoph Hellwig To: Amir Goldstein Cc: Christoph Hellwig , Andy Shevchenko , linux-fsdevel , Shaohua Li , Dan Williams , David Howells , Steven Whitehouse , Mimi Zohar , linux-xfs , linux-raid@vger.kernel.org, linux-nvdimm@ml01.01.org, linux-kernel , Hugh Dickins Subject: Re: [PATCH 23/23] uuid: remove uuid_be Message-ID: <20170518085629.GA6149@lst.de> References: <20170518062705.25902-1-hch@lst.de> <20170518062705.25902-24-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 18, 2017 at 10:57:24AM +0300, Amir Goldstein wrote: > I reviewed the entire series. You may add > Reviewed-by: Amir Goldstein > > to any of the patches as you see fit. Thanks, done! > Now let's talk about how this is going to be merged. > Do you intend to send Linus a pull request? Yes, that might be the best idea. I'm also contemplating listing me plus anyone volunteering (you?, Andy) as maintaines for the uuid code. But first I'll need a few more reviews, at least for the XFS bits. > Get those patches merged via someone else's tree? > Is this branch listed for linux-next build? Not yet. > The reason I am asking is because this last removal patch should probably > be applied near the end of the merge window (?). > Because maintainers cannot apply patches with code that uses the new > uuid_t to linux-next branches and we don't want linux-next build to fail > with new code that uses uuid_be... Yeah, we can probably defer that one for now. > More to the point, I would like to re-post the patch > ("tmpfs: generate random sb->s_uuid") using uuid_gen() > instead of generate_random_uuid() as you proposed. > Hugh has already acked the intent "once fs is agreed on the way to go" > When and how would I have this patch applied? > Obvious solution.. can you apply this patch to your branch? Yes. > Do you need me to re-post it? Please do.