All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: new tree for linux-next: uuid
Date: Mon, 5 Jun 2017 10:07:13 +0200	[thread overview]
Message-ID: <20170605080713.GA22028@lst.de> (raw)
In-Reply-To: <20170605094956.069d5af3@canb.auug.org.au>

Meh, thanks.  This has been throught the buildbot countless times
without a report.  But I guess a less generic name might be a good
idea to start with.

Andy: do you think UUID_INIT/GUID_INIT make sense to your?
or _INITIALIZER?

  reply	other threads:[~2017-06-05  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 20:14 new tree for linux-next: uuid Christoph Hellwig
2017-06-04 23:49 ` Stephen Rothwell
2017-06-05  8:07   ` Christoph Hellwig [this message]
2017-06-05 14:06     ` Andy Shevchenko
2017-06-05 14:29       ` Stephen Rothwell
2017-06-05 14:43         ` Andy Shevchenko
2017-06-05 14:55           ` Christoph Hellwig

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=20170605080713.GA22028@lst.de \
    --to=hch@lst.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.