From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: 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, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 3/4] Btrfs: Switch to use new generic UUID API
Date: Thu, 18 Jul 2019 20:38:42 +0300 [thread overview]
Message-ID: <20190718173842.GG9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190718172017.GA5868@x250>
On Thu, Jul 18, 2019 at 07:20:17PM +0200, Johannes Thumshirn wrote:
> On Wed, Jul 17, 2019 at 02:36:32PM +0300, Andy Shevchenko wrote:
> > There are new types and helpers that are supposed to be used in new code.
> >
> > As a preparation to get rid of legacy types and API functions do
> > the conversion here.
>
> Why? What was broken in the old versions? What benefit do we have apart from
> unneeded churn?
I think Christoph can explain this better than me.
By the way, if you look to the headers, there is no more "old" API, it's
covered as alias to the new one.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-07-18 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 11:36 [PATCH v3 1/4] uuid: Add inline helpers to import / export UUIDs Andy Shevchenko
2019-07-17 11:36 ` [PATCH v3 2/4] uuid: Provide a GUID generator for raw buffer Andy Shevchenko
2019-07-17 11:36 ` [PATCH v3 3/4] Btrfs: Switch to use new generic UUID API Andy Shevchenko
2019-07-18 17:20 ` Johannes Thumshirn
2019-07-18 17:38 ` Andy Shevchenko [this message]
2019-07-18 17:44 ` Johannes Thumshirn
2019-07-23 17:24 ` Andy Shevchenko
2019-07-17 11:36 ` [PATCH v3 4/4] uuid: Remove no more needed macro Andy Shevchenko
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=20190718173842.GG9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=jthumshirn@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox