From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uuid-types branch now stable
Date: Wed, 07 Jun 2017 20:06:36 +0300 [thread overview]
Message-ID: <1496855196.22624.50.camel@linux.intel.com> (raw)
In-Reply-To: <20170607155002.GA21662@lst.de>
On Wed, 2017-06-07 at 17:50 +0200, Christoph Hellwig wrote:
> Hi all,
>
> The uuid-types branch of git://git.infradead.org/users/hch/uuid.git
> will
> be immutable from now on, feel free to pull it into your trees.
>
> I plan to send the uuid changes to Linus as early as possible for the
> 4.13 merge window.
Thanks, Christoph!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-06-07 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 15:50 uuid-types branch now stable Christoph Hellwig
2017-06-07 17:06 ` Andy Shevchenko [this message]
2017-06-08 13:02 ` 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=1496855196.22624.50.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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