linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, kbuild test robot <fengguang.wu@intel.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix err_cast.cocci warnings
Date: Tue, 30 Jan 2018 07:11:54 +0800	[thread overview]
Message-ID: <30e63bf3-f496-6709-a13c-70fbeaefd687@oracle.com> (raw)
In-Reply-To: <20180129184055.GC19355@twin.jikos.cz>



On 01/30/2018 02:40 AM, David Sterba wrote:
> On Mon, Jan 29, 2018 at 02:50:10AM +0800, kbuild test robot wrote:
>> From: Fengguang Wu <fengguang.wu@intel.com>
>>
>> fs/btrfs/volumes.c:742:10-17: WARNING: ERR_CAST can be used with fs_devices
>>
>>
>>   Use ERR_CAST inlined function instead of ERR_PTR(PTR_ERR(...))
>>
>> Generated by: scripts/coccinelle/api/err_cast.cocci
>>
>> Fixes: bf155c98d312 ("btrfs: get device pointer from device_list_add()")
>> CC: Anand Jain <anand.jain@oracle.com>
>> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> 
> Thanks for the fix, I'll fold it to the patch.

  Oh. I just saw this email thread, err my filters. sorry.
  Thanks for the fix.

Anand

> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2018-01-29 23:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201801290206.Wy8wLcdm%fengguang.wu@intel.com>
2018-01-28 18:50 ` [PATCH] btrfs: fix err_cast.cocci warnings kbuild test robot
2018-01-29 18:40   ` David Sterba
2018-01-29 23:11     ` Anand Jain [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=30e63bf3-f496-6709-a13c-70fbeaefd687@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=fengguang.wu@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).