linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jiang Biao <jiang.biao2@zte.com.cn>
Cc: dedekind1@gmail.com, adrian.hunter@intel.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	zhong.weidong@zte.com.cn
Subject: Re: [PATCH] fs/ubifs: remove useless parameter of lpt_heap_replace
Date: Thu, 01 Mar 2018 17:23:41 +0100	[thread overview]
Message-ID: <3489822.spB4g6dZPN@blindfold> (raw)
In-Reply-To: <1519784557-105528-1-git-send-email-jiang.biao2@zte.com.cn>

Am Mittwoch, 28. Februar 2018, 03:22:37 CET schrieb Jiang Biao:
> The parameter *old_lprops* is never used in lpt_heap_replace(),
> remove it to avoid compile warning.

Makes sense. But what compiler warning do you get?

Thanks,
//richard

      reply	other threads:[~2018-03-01 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  2:22 [PATCH] fs/ubifs: remove useless parameter of lpt_heap_replace Jiang Biao
2018-03-01 16:23 ` Richard Weinberger [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=3489822.spB4g6dZPN@blindfold \
    --to=richard@nod.at \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=jiang.biao2@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=zhong.weidong@zte.com.cn \
    /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).