From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Lu Fengqi <lufq.fnst@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH v2 1/2] uuid: Add a glue layer macros for raw buffers
Date: Tue, 9 Apr 2019 12:25:12 +0200 [thread overview]
Message-ID: <20190409102512.GB7741@lst.de> (raw)
In-Reply-To: <20190404084526.GI9224@smile.fi.intel.com>
On Thu, Apr 04, 2019 at 11:45:26AM +0300, Andy Shevchenko wrote:
> On Wed, Apr 03, 2019 at 08:09:03PM +0200, Christoph Hellwig wrote:
> > On Fri, Mar 29, 2019 at 11:26:43PM +0300, Andy Shevchenko wrote:
> > > When the ID comes from or we would like to pass it to a raw buffer,
> > > the casting is needed.
> >
> > Something is missing in this sentence.
>
> What I meant there is if we got a raw buffer, consider u8 * pointer to it, and
> we would like to either take a UUID in binary form from it or pass it to that
> buffer, we have to cast due to type inequivalence.
>
> Can you suggest how to compress it nicely to few words?
Well, the usual way is to memcpy it out, and I'm not sure how this
is so much better. But maybe a detailed changelog that actuall parses
and properly typed inline functions might convince me :)
prev parent reply other threads:[~2019-04-09 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 20:26 [PATCH v2 1/2] uuid: Add a glue layer macros for raw buffers Andy Shevchenko
2019-04-03 18:09 ` Christoph Hellwig
2019-04-04 8:45 ` Andy Shevchenko
2019-04-09 10:25 ` 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=20190409102512.GB7741@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.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 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.