linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jan Kara <jack@suse.cz>, Jens Axboe <axboe@fb.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Paul Mackerras <paulus@samba.org>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: axonram: Delete an error message for a failed memory allocation in axon_ram_probe()
Date: Fri, 1 Sep 2017 17:13:58 +0200	[thread overview]
Message-ID: <15496bcd-1ad5-137c-5bb4-222b873a5992@users.sourceforge.net> (raw)
In-Reply-To: <3xkKq351vNz9t3P@ozlabs.org>

> Series applied to powerpc next, thanks.

Thanks for another positive feedback.

But I wonder how you can refer to the “series” when the forth update step
“Delete an unnecessary variable initialisation” contained a broken suggestion.


> https://git.kernel.org/powerpc/c/a1bddf3991573f3dff2762bfca5e11

This link seems to refer (only?) to the update step “Improve a size determination”.
How is the status for the other two change possibilities of this software module?

Regards,
Markus

  reply	other threads:[~2017-09-01 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 19:11 [PATCH 0/4] axonram: Adjustments for axon_ram_probe() SF Markus Elfring
2017-08-03 19:12 ` [PATCH 1/4] axonram: Delete an error message for a failed memory allocation in axon_ram_probe() SF Markus Elfring
2017-09-01 13:29   ` [1/4] " Michael Ellerman
2017-09-01 15:13     ` SF Markus Elfring [this message]
2017-08-03 19:14 ` [PATCH 2/4] axonram: Improve a size determination " SF Markus Elfring
2017-08-03 19:15 ` [PATCH 3/4] axonram: Return directly after a failed kzalloc() " SF Markus Elfring
2017-08-03 19:17 ` [PATCH 4/4] axonram: Delete an unnecessary variable initialisation " SF Markus Elfring
2017-08-04 13:12   ` kbuild test robot
2017-09-05 17:11     ` [PATCH v2] " SF Markus Elfring
2017-10-24  8:07       ` [v2] " Michael Ellerman
2017-08-04 16:51   ` [PATCH 4/4] " Tyrel Datwyler

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=15496bcd-1ad5-137c-5bb4-222b873a5992@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=axboe@fb.com \
    --cc=benh@kernel.crashing.org \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=patch-notifications@ellerman.id.au \
    --cc=paulus@samba.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).