From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>,
Amir Goldstein <amir73il@gmail.com>,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Yehezkel Bernat <yehezkel.bernat@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uuid updates for 4.13-rc
Date: Thu, 20 Jul 2017 12:09:13 +0300 [thread overview]
Message-ID: <1500541753.29303.129.camel@linux.intel.com> (raw)
In-Reply-To: <20170720075624.25619-1-hch@lst.de>
On Thu, 2017-07-20 at 09:56 +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series removes fixes a bug in the previous uuid pull request and
> removes the the uuid_be type. I had planned to send the
> last patch for -rc1 already but held off to avoid merge conflicts
> in linux-next.
>
> In the meantime the thunderbolt code added a few new instances, so
> patch once removes them. I'd like to get this small series into
> 4.13-rc so that 4.13 is released without the uuid_be type.
All patches in this series looks reasonable to me (1 is obvious bug fix,
2 is what we discussed with Mika, 3 obvious outcome).
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
I have sent uuid_le clean up, it looks I need to rebase it on top of
this series. Though I'm still waiting for comments, tags there...
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-07-20 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 7:56 Christoph Hellwig
2017-07-20 7:56 ` [PATCH 1/3] uuid: fix incorrect uuid_equal conversion in test_uuid_test Christoph Hellwig
2017-07-20 8:59 ` Amir Goldstein
2017-07-20 7:56 ` [PATCH 2/3] thunderbold: use uuid_t instead of uuid_be Christoph Hellwig
2017-07-20 9:01 ` Amir Goldstein
2017-07-24 9:28 ` Mika Westerberg
2017-07-24 15:50 ` Christoph Hellwig
2017-07-20 7:56 ` [PATCH 3/3] uuid: remove uuid_be Christoph Hellwig
2017-07-20 9:09 ` 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=1500541753.29303.129.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=amir73il@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=yehezkel.bernat@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
Powered by JetHome