From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jeremy Sowden <jeremy@azazel.net>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
devel@driverdev.osuosl.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/2] A couple additional patches for atomisp
Date: Sat, 30 May 2020 21:32:06 +0200 [thread overview]
Message-ID: <cover.1590866796.git.mchehab+huawei@kernel.org> (raw)
Patch 1 was sent by Arnd already, but, while it improved stack usage with
clang, it broke compilation with gcc ;-(
Each compiler seems to have different issues with different types of
struct initalizers, so we ended needing some discussions in order to find
something that would work for both.
So, the new version works fine with both compilers.
While here, I noticed a file that has nothing but comments. The second
patch gets rid of it.
Arnd Bergmann (1):
staging: media: atomisp: fix stack overflow in init_pipe_defaults()
Mauro Carvalho Chehab (1):
media: atomisp: get rid of sh_css_pipe.c
drivers/staging/media/atomisp/Makefile | 1 -
.../media/atomisp/pci/ia_css_frame_public.h | 6 ++---
.../staging/media/atomisp/pci/ia_css_pipe.h | 15 ++++-------
.../media/atomisp/pci/ia_css_pipe_public.h | 6 ++---
.../staging/media/atomisp/pci/ia_css_types.h | 6 ++---
.../sdis/common/ia_css_sdis_common_types.h | 9 +++----
.../runtime/binary/interface/ia_css_binary.h | 3 +--
.../pipeline/interface/ia_css_pipeline.h | 3 +--
.../pci/runtime/pipeline/src/pipeline.c | 13 ++++++---
drivers/staging/media/atomisp/pci/sh_css.c | 27 +++++++++++++------
.../staging/media/atomisp/pci/sh_css_pipe.c | 17 ------------
11 files changed, 46 insertions(+), 60 deletions(-)
delete mode 100644 drivers/staging/media/atomisp/pci/sh_css_pipe.c
--
2.26.2
next reply other threads:[~2020-05-30 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 19:32 Mauro Carvalho Chehab [this message]
2020-05-30 19:32 ` [PATCH 1/2] staging: media: atomisp: fix stack overflow in init_pipe_defaults() Mauro Carvalho Chehab
2020-05-30 19:32 ` [PATCH 2/2] media: atomisp: get rid of sh_css_pipe.c Mauro Carvalho Chehab
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.1590866796.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy@azazel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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 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).