public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Ulf Hansson <ulf.hansson@linaro.org>, linux-mmc@vger.kernel.org
Cc: Bojan Prtvar <prtvar.b@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Paul Burton <paul.burton@imgtec.com>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Uri Yanai <uri.yanai@sandisk.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: mmc: core: Delete an error message for a failed memory allocation in three functions
Date: Fri, 19 May 2017 09:39:12 +0000	[thread overview]
Message-ID: <50f3c642-b866-27f3-1201-5490225116f4@users.sourceforge.net> (raw)
In-Reply-To: <CAPDyKFqhNQdfr19195YfL7f4Jh0u6pGZ9QtSff0C6fe6R9wdjw@mail.gmail.com>

> It's a nice cleanup. However I found one more occasion in mmc_test.c,
> please fix that and re-spin.

To which source code place does this feedback refer?

Does it mean that another message removal would make sense in the
function “__mmc_test_register_dbgfs_file”?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mmc/core/mmc_test.c?h=v4.11#n3202

Regards,
Markus

  reply	other threads:[~2017-05-19  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13 12:54 [PATCH] mmc: core: Delete an error message for a failed memory allocation in three functions SF Markus Elfring
2017-05-13 17:24 ` Winkler, Tomas
2017-05-19  7:49 ` Ulf Hansson
2017-05-19  9:39   ` SF Markus Elfring [this message]
2017-05-19 10:00     ` Ulf Hansson
2017-05-19 11:34       ` [PATCH v2] mmc: core: Delete an error message for a failed memory allocation in four functions SF Markus Elfring
2017-05-22 12:03         ` Ulf Hansson

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=50f3c642-b866-27f3-1201-5490225116f4@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=paul.burton@imgtec.com \
    --cc=prtvar.b@gmail.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=tomas.winkler@intel.com \
    --cc=ulf.hansson@linaro.org \
    --cc=uri.yanai@sandisk.com \
    /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