From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH 0/4 RESEND 1-3/4 v5 4/4] btrfs, sysfs cleanup and add dev_state
Date: Thu, 6 Feb 2020 14:31:02 +0800 [thread overview]
Message-ID: <c0ac6404-ed46-be94-ac05-01c723f05134@oracle.com> (raw)
In-Reply-To: <20200203171659.GA2654@twin.jikos.cz>
On 2/4/20 1:16 AM, David Sterba wrote:
> On Mon, Feb 03, 2020 at 07:00:08PM +0800, Anand Jain wrote:
>> Resend:
>> Patch 4/4 is already integrated without the cleanup and preparatory
>> patches (1,2,3)/4. So I am resending those 3 patches. And the changes
>> in patch 4/4 as in misc-next is imported into patch v5 4/4 here. Patch
>> 4/4 has the details of the changes.
>
> All the patches have been merged and now are in linus/master branch.
David,
> I haven't reordered the patches so they're not in a group and the
> preparatory patches are about 10 commits above v5.5-rc7 which is the
> beginning of the branch.
It will cause problem during bisect, without the preparatory patches
the devid kobject lands under devices instead of under devinfo,
that's how I noticed that preparatory patches are missing.
Thanks, Anand
next prev parent reply other threads:[~2020-02-06 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 11:00 [PATCH 0/4 RESEND 1-3/4 v5 4/4] btrfs, sysfs cleanup and add dev_state Anand Jain
2020-02-03 11:00 ` [PATCH resend 1/4] btrfs: sysfs, use btrfs_sysfs_remove_fsid in fail return in add_fsid Anand Jain
2020-02-03 11:00 ` [PATCH resend 2/4] btrfs: sysfs, add UUID/devinfo kobject Anand Jain
2020-02-03 11:00 ` [PATCH resend v2 3/4] btrfs: sysfs, rename device_link add,remove functions Anand Jain
2020-02-03 11:00 ` [PATCH v5 4/4] btrfs: sysfs, add devid/dev_state kobject and device attribute Anand Jain
2020-02-03 17:16 ` [PATCH 0/4 RESEND 1-3/4 v5 4/4] btrfs, sysfs cleanup and add dev_state David Sterba
2020-02-06 6:31 ` Anand Jain [this message]
2020-02-06 14:11 ` David Sterba
2020-02-11 4:46 ` Anand Jain
2020-02-11 19:29 ` David Sterba
2020-02-12 9:29 ` Anand Jain
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=c0ac6404-ed46-be94-ac05-01c723f05134@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox