linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Dongliang Mu <dzm91@hust.edu.cn>, smatch@vger.kernel.org
Cc: Dan Carpenter <error27@gmail.com>, Vicki Pfau <vi@endrift.com>,
	kernel-janitors@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Pavel Rojtberg <rojtberg@gmail.com>, Nate Yocom <nate@yocom.org>,
	Mattijs Korpershoek <mkorpershoek@baylibre.com>,
	John Butler <radon86dev@gmail.com>,
	Matthias Benkmann <matthias.benkmann@gmail.com>,
	Christopher Crockett <chaorace@gmail.com>,
	Santosh De Massari <s.demassari@gmail.com>,
	hust-os-kernel-patches@googlegroups.com,
	syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com,
	"Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: xpad - fix GPF in xpad_probe
Date: Tue, 2 May 2023 13:34:12 +0300	[thread overview]
Message-ID: <f103fc8e-8cf5-435a-92db-56691c8164fe@kili.mountain> (raw)
In-Reply-To: <f71f3012-916c-5271-b908-feeee5a85a46@hust.edu.cn>

On Sun, Apr 23, 2023 at 10:33:29AM +0800, Dongliang Mu wrote:
> BTW, do you have any plans to improve the code readability, directory
> orgranization, documentation etc. of Smatch? It's hard even for senior
> students to start with.

I have created some documentation.  Read the following blogs in order:

https://staticthinking.wordpress.com/2023/04/24/smatch-data-types/
https://staticthinking.wordpress.com/2023/04/25/first-smatch-check/
https://staticthinking.wordpress.com/2023/04/25/merging-states/
https://staticthinking.wordpress.com/2023/05/02/the-cross-function-db/
https://staticthinking.wordpress.com/2023/05/02/the-param-key-api/
https://staticthinking.wordpress.com/2023/05/02/smatch-hooks-and-modules/
https://staticthinking.wordpress.com/2023/05/02/debugging-smatch-checks/

Email the smatch@vger.kernel.org mailing list with any questions.

regards,
dan carpenter


  reply	other threads:[~2023-05-02 10:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 12:55 [PATCH] Input: xpad - fix GPF in xpad_probe Dongliang Mu
2023-04-17  9:25 ` Dan Carpenter
     [not found]   ` <99794af0-7367-acff-357d-1cd4fa7f832e@hust.edu.cn>
2023-04-17 10:24     ` Vicki Pfau
     [not found]       ` <57577302-8d18-231f-062b-b1d262720943@hust.edu.cn>
2023-04-17 11:07         ` Vicki Pfau
2023-04-17 11:15           ` Dongliang Mu
2023-04-17 10:42   ` Dan Carpenter
2023-04-20 11:07     ` Dan Carpenter
2023-04-22 19:48       ` Dan Carpenter
2023-04-22 19:56         ` Dan Carpenter
2023-04-23  2:33         ` Dongliang Mu
2023-05-02 10:34           ` Dan Carpenter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14 21:12 Claudia De-Massari

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=f103fc8e-8cf5-435a-92db-56691c8164fe@kili.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=chaorace@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dzm91@hust.edu.cn \
    --cc=error27@gmail.com \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.benkmann@gmail.com \
    --cc=mkorpershoek@baylibre.com \
    --cc=nate@yocom.org \
    --cc=pgriffais@valvesoftware.com \
    --cc=radon86dev@gmail.com \
    --cc=rojtberg@gmail.com \
    --cc=s.demassari@gmail.com \
    --cc=smatch@vger.kernel.org \
    --cc=syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com \
    --cc=vi@endrift.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).