From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christoph Hellwig <hch@lst.de>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the uuid tree
Date: Mon, 5 Jun 2017 16:41:58 +0200 [thread overview]
Message-ID: <20170605144158.GA28659@lst.de> (raw)
In-Reply-To: <1496673610.22624.7.camel@linux.intel.com>
On Mon, Jun 05, 2017 at 05:40:10PM +0300, Andy Shevchenko wrote:
> On Mon, 2017-06-05 at 16:09 +1000, Stephen Rothwell wrote:
> > Hi Christoph,
> >
> > After merging the uuid tree, today's linux-next build (arm
> > multi_v7_defconfig and x86_64 allmodconfig) produced these warnings:
> >
>
> Briefly looking to the conflict it looks like we first need to rename
> register description(s) in dwc2 in the way how it's done in dwc3.
They probably should do that. But I also think GUID and UUID
are too generic names for a macro and would like to change them
in uuid.h
prev parent reply other threads:[~2017-06-05 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 6:09 linux-next: build warnings after merge of the uuid tree Stephen Rothwell
2017-06-05 14:40 ` Andy Shevchenko
2017-06-05 14:41 ` Christoph Hellwig [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=20170605144158.GA28659@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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