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@xxxxxxxxx>
>
> 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.
