public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Alexander Graf <graf@amazon.com>,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1 1/1] mei: Move uuid.h to the MEI namespace
Date: Fri, 17 Mar 2023 16:12:13 +0200	[thread overview]
Message-ID: <ZBR1PWRY7ql7VIth@smile.fi.intel.com> (raw)
In-Reply-To: <ZBR0MVcQrokpSoRp@kroah.com>

On Fri, Mar 17, 2023 at 03:07:45PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 10, 2023 at 07:07:47PM +0200, Andy Shevchenko wrote:
> > There is only a single user of the UUID uAPI, let's make it
> > part of that user.
> > 
> > The way it's done is to prevent compilation time breakage for
> > the user space that does
> > 
> > 	#include <linux/uuid.h>
> > 
> > In the future MEI user space tools can switch over to use mei_uuid.h.
> 
> When will that happen?

I don't know

> And why the churn, what's the problem with keeping this as uuid.h?

The problem here is a possible confusion with uAPI and internal headers with
the same name.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2023-03-17 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 17:07 [PATCH v1 1/1] mei: Move uuid.h to the MEI namespace Andy Shevchenko
2023-03-17 14:07 ` Greg Kroah-Hartman
2023-03-17 14:12   ` 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=ZBR1PWRY7ql7VIth@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=arnd@arndb.de \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=graf@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    --cc=vitaly.lubart@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