From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: james.smart@emulex.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 14/21] lpfc: Fix premature release of rpi bit in bitmask
Date: Sat, 07 Mar 2015 09:11:42 -0800 [thread overview]
Message-ID: <1425748302.2969.15.camel@HansenPartnership.com> (raw)
In-Reply-To: <1423164309.7917.38.camel@myfc17>
On Thu, 2015-02-05 at 14:25 -0500, James Smart wrote:
> ---
This is a bit big for an empty explanation. You're adding a lot of
unexplained debug statements, but your own words in the comment seem to
be the best changelog:
> + * lpfc_sli4_unreg_rpi_cmpl_clr - mailbox completion handler
> + * @phba: Pointer to HBA context object.
> + * @pmb: Pointer to mailbox object.
> + *
> + * This function is the unreg rpi mailbox completion handler. It
> + * frees the memory resources associated with the completed mailbox
> + * command. An additional refrenece is put on the ndlp to prevent
> + * lpfc_nlp_release from freeing the rpi bit in the bitmask before
> + * the unreg mailbox command completes, this routine puts the
> + * reference back.
I know its in the code, but the reason we have changelogs is so that
when distros ask "is this fixed upstream" they can look through the git
log for the driver to get an idea. For them you need to say that this
is SLI rev 4 only and then give the above explanation.
James
next prev parent reply other threads:[~2015-03-07 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 19:25 [PATCH 14/21] lpfc: Fix premature release of rpi bit in bitmask James Smart
2015-03-07 17:11 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-03 21:12 James Smart
2015-04-10 6:18 ` Hannes Reinecke
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=1425748302.2969.15.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=james.smart@emulex.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;
as well as URLs for NNTP newsgroup(s).