From: Aishwarya Pant <aishpant@gmail.com>
To: Alan Cox <alan@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: outreachy-kernel@googlegroups.com
Subject: [PATCH v3 0/2] staging: atomisp: memory allocation cleanups
Date: Tue, 17 Oct 2017 18:43:38 +0530 [thread overview]
Message-ID: <cover.1508245883.git.aishpant@gmail.com> (raw)
Patch series performs minor code cleanups using coccinelle to simplify memory
allocation tests and remove redundant OOM log messages.
Changes in v3:
Rebase changes over atomisp-next branch of the media tree
Changes in v2:
Rebase and re-send patches
Aishwarya Pant (2):
staging: atomisp2: cleanup null check on memory allocation
staging: atomisp: cleanup out of memory messages
drivers/staging/media/atomisp/i2c/atomisp-ap1302.c | 4 +--
drivers/staging/media/atomisp/i2c/atomisp-gc0310.c | 4 +--
drivers/staging/media/atomisp/i2c/atomisp-gc2235.c | 4 +--
drivers/staging/media/atomisp/i2c/atomisp-lm3554.c | 4 +--
.../staging/media/atomisp/i2c/atomisp-mt9m114.c | 4 +--
drivers/staging/media/atomisp/i2c/atomisp-ov2680.c | 4 +--
drivers/staging/media/atomisp/i2c/atomisp-ov2722.c | 4 +--
drivers/staging/media/atomisp/i2c/imx/imx.c | 4 +--
.../media/atomisp/i2c/ov5693/atomisp-ov5693.c | 4 +--
drivers/staging/media/atomisp/i2c/ov8858.c | 6 +---
.../media/atomisp/pci/atomisp2/atomisp_fops.c | 4 +--
.../media/atomisp/pci/atomisp2/atomisp_ioctl.c | 9 ++----
.../media/atomisp/pci/atomisp2/css2400/sh_css.c | 36 +++++++++++-----------
.../atomisp/pci/atomisp2/css2400/sh_css_firmware.c | 7 ++---
.../pci/atomisp2/css2400/sh_css_param_shading.c | 4 +--
.../media/atomisp/pci/atomisp2/hmm/hmm_bo.c | 10 ++----
.../atomisp/pci/atomisp2/hmm/hmm_dynamic_pool.c | 6 +---
.../atomisp/pci/atomisp2/hmm/hmm_reserved_pool.c | 5 +--
.../media/atomisp/pci/atomisp2/hmm/hmm_vm.c | 4 +--
.../platform/intel-mid/atomisp_gmin_platform.c | 4 +--
20 files changed, 41 insertions(+), 90 deletions(-)
--
2.11.0
next reply other threads:[~2017-10-17 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 13:13 Aishwarya Pant [this message]
2017-10-17 13:14 ` [PATCH v3 1/2] staging: atomisp2: cleanup null check on memory allocation Aishwarya Pant
2017-10-17 13:14 ` [PATCH v3 2/2] staging: atomisp: cleanup out of memory messages Aishwarya Pant
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.1508245883.git.aishpant@gmail.com \
--to=aishpant@gmail.com \
--cc=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sakari.ailus@linux.intel.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.