Powered by Linux

Re: Smatch - possible regression in unreachable code check — Semantic Matching Tool

Re: Smatch - possible regression in unreachable code check

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Smatch - possible regression in unreachable code check
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Date: Tue, 29 Oct 2024 16:40:35 +0300
Cc: smatch@xxxxxxxxxxxxxxx, Dan Carpenter <error27@xxxxxxxxx>
In-reply-to: <c9db770e-7b5b-4472-8ac7-b2551637de85@stanley.mountain>
References: <73bbd210-58a2-446b-8b3f-4b3639203650@oracle.com> <c9db770e-7b5b-4472-8ac7-b2551637de85@stanley.mountain>

Okay, I've pushed this.  But the unfortunate thing is that if you rebuilt the
data with yesterday's linux-next the smatch_db.sqlite database and the
smatch_data/kernel.no_return_funcs file will be messed up.

regards,
dan carpenter

References:
- Smatch - possible regression in unreachable code check
  - From: Harshit Mogalapalli
- Re: Smatch - possible regression in unreachable code check
  - From: Dan Carpenter

Prev by Date: Re: Smatch - possible regression in unreachable code check
Next by Date: update check_cmn_err
Previous by thread: Re: Smatch - possible regression in unreachable code check
Next by thread: update check_cmn_err
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI] [Big List of Linux Books]

Powered by Linux