From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Dupuis, Chad" <chad.dupuis@cavium.com>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
james.bottomley@hansenpartnership.com, hare@suse.de,
QLogic-Storage-Upstream@cavium.com
Subject: Re: [PATCH] qedf: fixup compilation warning about atomic_t usage
Date: Thu, 23 Feb 2017 16:59:38 -0500 [thread overview]
Message-ID: <yq11suo7elx.fsf@oracle.com> (raw)
In-Reply-To: <1487862063-28158-1-git-send-email-chad.dupuis@cavium.com> (Chad Dupuis's message of "Thu, 23 Feb 2017 07:01:03 -0800")
>>>>> "Chad" == Dupuis, Chad <chad.dupuis@cavium.com> writes:
Chad> The driver didn't follow the atomic_t vs refcount_t change, and
Chad> anyway one should be using kref_read() instead of accessing the
Chad> counter inside an kref.
Applied to 4.11/scsi-fixes.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-02-23 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 15:01 [PATCH] qedf: fixup compilation warning about atomic_t usage Dupuis, Chad
2017-02-23 21:59 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-23 11:44 Hannes Reinecke
2017-02-23 14:43 ` Chad Dupuis
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=yq11suo7elx.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=chad.dupuis@cavium.com \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@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