From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
linuxppc-dev@lists.ozlabs.org,
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>
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [1/4] axonram: Delete an error message for a failed memory allocation in axon_ram_probe()
Date: Fri, 1 Sep 2017 23:29:51 +1000 (AEST) [thread overview]
Message-ID: <3xkKq351vNz9t3P@ozlabs.org> (raw)
In-Reply-To: <31790d2a-26b4-54f5-e52d-5637be0b676f@users.sourceforge.net>
On Thu, 2017-08-03 at 19:12:50 UTC, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Thu, 3 Aug 2017 19:49:18 +0200
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/a1bddf3991573f3dff2762bfca5e11
cheers
next prev parent reply other threads:[~2017-09-01 13:29 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 ` Michael Ellerman [this message]
2017-09-01 15:13 ` SF Markus Elfring
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=3xkKq351vNz9t3P@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=axboe@fb.com \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=elfring@users.sourceforge.net \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).