public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <robert.w.love@intel.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: devel@open-fcoe.org, linux-scsi@vger.kernel.org
Subject: Re: [Open-FCoE] [PATCH] libfc: add stats info against memory leakage in exchange pool
Date: Wed, 27 Oct 2010 17:49:42 -0700	[thread overview]
Message-ID: <1288226982.1431.19.camel@fritz> (raw)
In-Reply-To: <AANLkTi=QbmJM7qCFnAvdVXcE=4sprA7MtMzMLvHvtxmd@mail.gmail.com>

On Tue, 2010-10-26 at 21:24 +0800, Hillf Danton wrote:
> This is the second version, with a fault in the previous version fixed.
> 
> Signed-off-by: Hillf Danton <dhillf@gmail.com>
> ---
> 

This patch fails to apply on top of your other patch that adds a
exchange cache. I have fixed it locally and will add the fixed patch to
fcoe-next. You also omitted any patch description in this patch other
than it being the second version.

Can you please add more verbose descriptions to your patches. The best
advice given to me was to have a problem statement, a statement on what
the solution is and then any technical details. I realize that some of
your patches are very straight-forward and don't require that degree of
detail, but some have been a bit more involved and "seems like there is
a problem" doesn't give much context before looking at the changes
themselves. It would help me when reviewing your changes.

Thanks, //Rob


  reply	other threads:[~2010-10-28  0:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24  9:30 [PATCH] libfc: add stats info against memory leakage in exchange pool Hillf Danton
2010-10-26 13:24 ` Hillf Danton
2010-10-28  0:49   ` Robert Love [this message]
2010-10-28 13:53     ` [Open-FCoE] " Hillf Danton

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=1288226982.1431.19.camel@fritz \
    --to=robert.w.love@intel.com \
    --cc=devel@open-fcoe.org \
    --cc=dhillf@gmail.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