From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>, Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Shaohua Li <shli@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
David Howells <dhowells@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-raid@vger.kernel.org, linux-nvdimm@lists.01.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 23/23] uuid: remove uuid_be
Date: Mon, 22 May 2017 21:59:25 +0300 [thread overview]
Message-ID: <1495479565.6967.72.camel@linux.intel.com> (raw)
In-Reply-To: <20170518085629.GA6149@lst.de>
On Thu, 2017-05-18 at 10:56 +0200, Christoph Hellwig wrote:
> 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 <amir73il@gmail.com>
> >
> > to any of the patches as you see fit.
>
> Thanks, done!
Similar from my side, FWIW:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> > 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.
I would agree to be a designated reviewer for now (too many stuff to
follow as a (co-)maintainer).
> > 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.
I would also like to append some of patches from my side, though they
are WIP.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-05-22 18:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 6:26 cleanup UUID types V3 Christoph Hellwig
2017-05-18 6:26 ` [PATCH 01/23] xfs: use uuid_copy() helper to abstract uuid_t Christoph Hellwig
2017-05-18 13:27 ` Brian Foster
2017-05-18 23:32 ` Darrick J. Wong
2017-05-18 6:26 ` [PATCH 02/23] xfs: use uuid_be to implement the uuid_t type Christoph Hellwig
2017-05-18 13:27 ` Brian Foster
2017-05-18 23:34 ` Darrick J. Wong
2017-05-18 6:26 ` [PATCH 03/23] uuid: remove uuid_be defintions from the uapi header Christoph Hellwig
2017-05-18 7:12 ` Joe Perches
2017-05-18 7:13 ` Christoph Hellwig
2017-05-19 10:58 ` David Howells
2017-05-21 6:55 ` Christoph Hellwig
2017-05-18 6:26 ` [PATCH 04/23] uuid: rename uuid types Christoph Hellwig
2017-05-18 17:42 ` Darrick J. Wong
2017-05-18 6:26 ` [PATCH 05/23] uuid: don't export guid_index and uuid_index Christoph Hellwig
2017-05-18 6:26 ` [PATCH 06/23] uuid: add the v1 layout to uuid_t Christoph Hellwig
2017-05-18 6:26 ` [PATCH 07/23] uuid: hoist helpers uuid_equal() and uuid_copy() from xfs Christoph Hellwig
2017-05-18 6:26 ` [PATCH 08/23] uuid: hoist uuid_is_null() helper from libnvdimm Christoph Hellwig
2017-05-18 6:26 ` [PATCH 09/23] S390/sysinfo: use uuid_is_null instead of opencoding it Christoph Hellwig
2017-05-18 6:26 ` [PATCH 10/23] afs: switch to use uuid_t and uuid_gen Christoph Hellwig
2017-05-22 18:49 ` Andy Shevchenko
2017-05-23 8:49 ` Christoph Hellwig
2017-05-23 13:11 ` Andy Shevchenko
2017-05-25 13:00 ` Christoph Hellwig
2017-05-25 13:29 ` Andy Shevchenko
2017-05-18 6:26 ` [PATCH 11/23] uuid: remove struct uuid_v1 Christoph Hellwig
2017-05-18 6:26 ` [PATCH 12/23] xfs: remove uuid_getnodeuniq and xfs_uu_t Christoph Hellwig
2017-05-18 13:27 ` Brian Foster
2017-05-18 23:35 ` Darrick J. Wong
2017-05-18 6:26 ` [PATCH 13/23] md: namespace private helper names Christoph Hellwig
2017-05-18 18:32 ` Shaohua Li
2017-05-22 18:52 ` Andy Shevchenko
2017-05-23 8:41 ` Christoph Hellwig
2017-05-18 6:26 ` [PATCH 14/23] xfs: use the common helper uuid_is_null() Christoph Hellwig
2017-05-18 13:27 ` Brian Foster
2017-05-18 6:26 ` [PATCH 15/23] block: remove blk_part_pack_uuid Christoph Hellwig
2017-05-18 23:15 ` Mimi Zohar
2017-05-18 6:26 ` [PATCH 16/23] ima/policy: switch to use uuid_t Christoph Hellwig
2017-05-18 23:16 ` Mimi Zohar
2017-05-18 6:26 ` [PATCH 17/23] fs: switch ->s_uuid to uuid_t Christoph Hellwig
2017-05-18 23:17 ` Mimi Zohar
2017-05-18 6:27 ` [PATCH 18/23] overlayfs: use uuid_t instead of uuid_be Christoph Hellwig
2017-05-18 6:27 ` [PATCH 19/23] partitions/ldm: switch to use uuid_t Christoph Hellwig
2017-05-18 6:27 ` [PATCH 20/23] sysctl: " Christoph Hellwig
2017-05-18 6:27 ` [PATCH 21/23] nvme: switch to uuid_t Christoph Hellwig
2017-05-18 6:27 ` [PATCH 22/23] scsi_debug: " Christoph Hellwig
2017-05-18 6:27 ` [PATCH 23/23] uuid: remove uuid_be Christoph Hellwig
2017-05-18 7:57 ` Amir Goldstein
2017-05-18 8:56 ` Christoph Hellwig
2017-05-22 18:59 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1495479565.6967.72.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=amir73il@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=shli@kernel.org \
--cc=swhiteho@redhat.com \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).