From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v5 0/9] Misc props.c cleanups
Date: Tue, 12 Mar 2019 19:12:24 +0800 [thread overview]
Message-ID: <d32bb7bd-e588-76ce-c07b-b263eb63f8cd@oracle.com> (raw)
In-Reply-To: <20190311144116.GW31119@twin.jikos.cz>
On 3/11/19 10:41 PM, David Sterba wrote:
> On Sat, Mar 09, 2019 at 08:04:14AM +0800, Anand Jain wrote:
>> On 3/8/19 11:01 PM, David Sterba wrote:
>>> On Fri, Mar 01, 2019 at 12:34:46PM +0800, Anand Jain wrote:
>>>> v5: drops patch
>>>> [PATCH v4 03/10] btrfs: trivial, fix c coding style
>>>> Chanegs are mainly to use BUG_ON instead of ASSERT as in the
>>>> original code in patches 5-7/9. Fix ASSERT in 8/9. And add
>>>> a rename in 9/9. Each individual patches as the details of
>>>> the changes.
>>>
>>> The cleanup makes it easier to follow and the transaction semantics is
>>> more visible, good.
>>>
>>> I've fixed up the small things commented under the patches, no need to
>>> resend. Patchset added to 5.2 queue, thanks.
>>>
>>
>> Thanks for the feedback, review and integration.
>>
>> Just checked these branches scrub-misc, misc-next, for-next-20190307
>> any idea which branch these patches went to.
>
> It's in a local topic branch and will appear in for-next once the merge
> window is over. I've pushed it out now as ext/anand/cleanup-props-v5 so
> you can have a look.
Thanks. Patches [1-9]/9 Looks good.
next prev parent reply other threads:[~2019-03-12 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 4:34 [PATCH v5 0/9] Misc props.c cleanups Anand Jain
2019-03-01 4:34 ` [PATCH v5 1/9] btrfs: kill __btrfs_set_prop() Anand Jain
2019-03-01 4:34 ` [PATCH v5 2/9] btrfs: drop redundant forward declaration in props.c Anand Jain
2019-03-01 4:34 ` [PATCH v5 3/9] btrfs: rename fs_info argument to fs_private Anand Jain
2019-03-01 4:34 ` [PATCH v5 4/9] btrfs: refactor btrfs_set_prop add btrfs_set_prop_trans Anand Jain
2019-03-08 14:49 ` David Sterba
2019-03-01 4:34 ` [PATCH v5 5/9] btrfs: start transaction in btrfs_set_prop_trans Anand Jain
2019-03-01 4:34 ` [PATCH v5 6/9] btrfs: start transaction in btrfs_set_acl Anand Jain
2019-03-08 14:52 ` David Sterba
2019-03-01 4:34 ` [PATCH v5 7/9] btrfs: start transaction in btrfs_xattr_handler_set Anand Jain
2019-03-01 4:34 ` [PATCH v5 8/9] btrfs: btrfs_setxattr argument trans is never NULL Anand Jain
2019-03-01 4:34 ` [PATCH v5 9/9] btrfs: kill btrfs_setxattr Anand Jain
2019-03-08 14:56 ` David Sterba
2019-03-09 1:18 ` Anand Jain
2019-03-08 15:01 ` [PATCH v5 0/9] Misc props.c cleanups David Sterba
2019-03-09 0:04 ` Anand Jain
2019-03-11 14:41 ` David Sterba
2019-03-12 11:12 ` Anand Jain [this message]
2019-03-12 17:22 ` David Sterba
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=d32bb7bd-e588-76ce-c07b-b263eb63f8cd@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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.