All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgiana Chelu <georgiana.chelu93@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v2 00/10] Fix checkpatch issues
Date: Tue, 26 Sep 2017 09:01:28 -0700	[thread overview]
Message-ID: <cover.1506436974.git.georgiana.chelu93@gmail.com> (raw)

This patchset was created on Julia recommendation to
remove 'out of memory' messages and unlikely checks.

* [1/10] kmalloc generates a backtrace on failure and it will
show the same information as the removed messages.
* [2/10] unlikely checks are not necessary on NULL pointers
after a memory allocation.

Also, new changes were made to improve the code from hmm_bo.c file.
Some of the issues were already in the file, others were introduced
on previous patches of this set.
These new changes are available on [3/10-10/10] patches.

Changes in v2:
* Nothing changed in 1/10
* New added 2/10 - 10/10


Georgiana Chelu (10):
  Staging: media: atomisp: Use kmalloc_array instead of kmalloc
  Staging: media: atomisp: Remove useless 'out of memory' messages
  Staging: media: atomisp: Remove unlikely from NULL pointer check
  Staging: media: atomisp: Adjust checks for null pointers
  Staging: media: atomisp: Remove return statement from void function
  Staging: media: atomisp: Add spaces around bitwise OR
  Staging: media: atomisp: Remove braces {} for single statement blocks
  Staging: media: atomisp: Align code with open parenthesis
  Staging: media: atomisp: Merge quoted string split across lines
  Staging: media: atomisp: Split lines wiht over 80 characters

 .../media/atomisp/pci/atomisp2/hmm/hmm_bo.c        | 164 ++++++++++-----------
 1 file changed, 76 insertions(+), 88 deletions(-)

-- 
2.7.4



             reply	other threads:[~2017-09-26 16:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 16:01 Georgiana Chelu [this message]
2017-09-26 16:01 ` [PATCH v2 01/10] Staging: media: atomisp: Use kmalloc_array instead of kmalloc Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 02/10] Staging: media: atomisp: Remove useless 'out of memory' messages Georgiana Chelu
2017-09-29 13:34   ` [Outreachy kernel] " Greg Kroah-Hartman
2017-10-01 11:37     ` Georgiana Chelu
2017-10-01 11:47       ` Julia Lawall
2017-10-01 11:56         ` Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 03/10] Staging: media: atomisp: Remove unlikely from NULL pointer check Georgiana Chelu
2017-09-29 13:35   ` Greg Kroah-Hartman
2017-09-26 16:01 ` [PATCH v2 04/10] Staging: media: atomisp: Adjust checks for null pointers Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 05/10] Staging: media: atomisp: Remove return statement from void function Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 06/10] Staging: media: atomisp: Add spaces around bitwise OR Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 07/10] Staging: media: atomisp: Remove braces {} for single statement blocks Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 08/10] Staging: media: atomisp: Align code with open parenthesis Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 09/10] Staging: media: atomisp: Merge quoted string split across lines Georgiana Chelu
2017-09-26 16:01 ` [PATCH v2 10/10] Staging: media: atomisp: Split lines wiht over 80 characters Georgiana Chelu

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=cover.1506436974.git.georgiana.chelu93@gmail.com \
    --to=georgiana.chelu93@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=mchehab@kernel.org \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.