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 v3 0/7] Fix checkpatch issues
Date: Mon, 2 Oct 2017 00:34:35 +0300 [thread overview]
Message-ID: <cover.1506891671.git.georgiana.chelu93@gmail.com> (raw)
This patchset was created to fix warnings introduced
by several patches from the previous patchset.
The number of the patches was reduced from 10 to 7
because 1 patch is already accepted, 2 patches were
combined into a single patch, and the changes from
the 10/10 patch were added in the patches where
coding style fixes were required.
* [1/07] kmalloc generates a backtrace on failure and it will
show the same information as the removed messages.
* [2/07] the unlikely function is not necessary on NULL pointers
after a memory allocation.
Changes in v2:
* Nothing changed in 1/10
* New added 2/10 - 10/10
Changes in v3:
* added a different cover letter message
* removed an accepted patch
* removed the braces for single statement blocks in 1/7
* split the lines with over 80 characters where changes
were made
Georgiana Chelu (7):
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: Merge quoted string split across lines
Staging: media: atomisp: Align code with open parenthesis
.../media/atomisp/pci/atomisp2/hmm/hmm_bo.c | 156 ++++++++++-----------
1 file changed, 72 insertions(+), 84 deletions(-)
--
2.11.0
next reply other threads:[~2017-10-01 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 21:34 Georgiana Chelu [this message]
2017-10-01 21:34 ` [PATCH v3 1/7] Staging: media: atomisp: Remove useless 'out of memory' messages Georgiana Chelu
2017-10-01 21:34 ` [PATCH v3 2/7] Staging: media: atomisp: Remove unlikely from NULL pointer check Georgiana Chelu
2017-10-01 21:34 ` [PATCH v3 3/7] Staging: media: atomisp: Adjust checks for null pointers Georgiana Chelu
2017-10-01 21:34 ` [PATCH v3 4/7] Staging: media: atomisp: Remove return statement from void function Georgiana Chelu
2017-10-01 21:34 ` [PATCH v3 5/7] Staging: media: atomisp: Add spaces around bitwise OR Georgiana Chelu
2017-10-01 21:34 ` [PATCH v3 6/7] Staging: media: atomisp: Merge quoted string split across lines Georgiana Chelu
2017-10-03 16:15 ` Greg Kroah-Hartman
2017-10-01 21:34 ` [PATCH v3 7/7] Staging: media: atomisp: Align code with open parenthesis Georgiana Chelu
2017-10-03 16:09 ` [PATCH v3 0/7] Fix checkpatch issues Greg Kroah-Hartman
2017-10-07 21:31 ` 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.1506891671.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.