From: Dan Carpenter <dan.carpenter@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Anton Bambura <jenneron@protonmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] media: staging: tegra-vde: Support reference picture marking
Date: Thu, 18 Nov 2021 09:53:15 +0300 [thread overview]
Message-ID: <20211118065315.GP26989@kadam> (raw)
In-Reply-To: <cec5c6cf048eacec2c8204b99c5708996fa9f178.camel@perches.com>
On Wed, Nov 17, 2021 at 10:21:00PM -0800, Joe Perches wrote:
> On Thu, 2021-11-18 at 09:14 +0300, Dan Carpenter wrote:
> > It's not hard to run Smatch yourself...
> >
> > Depending on if you're on a apt distro or yum distro then fetch the
> > dependencies with one of the follow commands:
> > apt-get install gcc make sqlite3 libsqlite3-dev libdbd-sqlite3-perl libssl-dev libtry-tiny-perl
> > yum install gcc make sqlite3 sqlite-devel sqlite perl-DBD-SQLite openssl-devel perl-Try-Tiny
> >
> > git clone https://github.com/error27/smatch
> > cd smatch
> > make
> > cd ~/kernel_source/
> > ~/smatch/smatch_scripts/kchecker drivers/subsystem/
>
> Might want to stick something in Documentation about that.
>
That's a good idea. I was trying to figure out where it should go and
I looked at Documentation/process/submit-checklist.rst and point 4 had
me a bit puzzled:
4) ppc64 is a good architecture for cross-compilation checking because it
tends to use ``unsigned long`` for 64-bit quantities.
It took me a while to realize that this must have been written when 64
bit systems were new and rare. :P This documentation is old old old...
regards,
dan carpenter
next prev parent reply other threads:[~2021-11-18 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 22:23 [PATCH v1 0/3] Add NVIDIA Tegra114 support to video decoder driver Dmitry Osipenko
2021-11-14 22:23 ` [PATCH v1 1/3] media: staging: tegra-vde: Support reference picture marking Dmitry Osipenko
2021-11-14 22:34 ` Dmitry Osipenko
2021-11-15 12:44 ` Dan Carpenter
2021-11-15 14:34 ` Dmitry Osipenko
2021-11-15 15:48 ` Dan Carpenter
2021-11-17 16:19 ` Dmitry Osipenko
2021-11-18 6:07 ` Dan Carpenter
2021-11-18 6:14 ` Dan Carpenter
2021-11-18 6:21 ` Joe Perches
2021-11-18 6:53 ` Dan Carpenter [this message]
2021-11-18 6:55 ` Dan Carpenter
2021-11-18 13:56 ` Dmitry Osipenko
2021-11-19 12:30 ` Dan Carpenter
2021-11-19 16:14 ` Dmitry Osipenko
2021-11-14 22:23 ` [PATCH v1 2/3] media: staging: tegra-vde: Properly mark invalid entries Dmitry Osipenko
2021-11-14 22:23 ` [PATCH v1 3/3] media: staging: tegra-vde: Reorder misc device registration Dmitry Osipenko
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=20211118065315.GP26989@kadam \
--to=dan.carpenter@oracle.com \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jenneron@protonmail.com \
--cc=joe@perches.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=thierry.reding@gmail.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