Skip to content
Snippets Groups Projects
Commit c1929462 authored by chrfranke's avatar chrfranke
Browse files

drivedb.h: Innodisk 1IE3/3IE3/3ME3/3IE4/3ME4 SSDs: Ensure that

opening and closing brackets are in the same line (#1495).

git-svn-id: https://svn.code.sf.net/p/smartmontools/code/trunk@5360 4ea69e1a-61f1-4043-bf83-b5c94c648137
parent fdbc0d99
No related branches found
No related tags found
No related merge requests found
...@@ -2,6 +2,9 @@ $Id$ ...@@ -2,6 +2,9 @@ $Id$
2022-04-24 Christian Franke <franke@computer.org> 2022-04-24 Christian Franke <franke@computer.org>
drivedb.h: Innodisk 1IE3/3IE3/3ME3/3IE4/3ME4 SSDs: Ensure that
opening and closing brackets are in the same line (#1495).
update-smart-drivedb.in: Unify syntax of command substitutions. update-smart-drivedb.in: Unify syntax of command substitutions.
update-smart-drivedb.in: Don't use 'let' which is bash specific. update-smart-drivedb.in: Don't use 'let' which is bash specific.
......
...@@ -1110,8 +1110,8 @@ const drive_settings builtin_knowndrives[] = { ...@@ -1110,8 +1110,8 @@ const drive_settings builtin_knowndrives[] = {
// mSATA 3ME4/L16711, M.2 (S42) 3ME4/L16711, SATADOM-MH 3ME4/L16B01, // mSATA 3ME4/L16711, M.2 (S42) 3ME4/L16711, SATADOM-MH 3ME4/L16B01,
// SATADOM-SH 3ME4/L16B01, SATADOM-SH Type C 3ME4/L16B01, SATADOM-SH Type D 3ME4/L16B01, // SATADOM-SH 3ME4/L16B01, SATADOM-SH Type C 3ME4/L16B01, SATADOM-SH Type D 3ME4/L16B01,
// mSATA 3IE4/L16B01Hi // mSATA 3IE4/L16B01Hi
"(2.5\" SATA SSD|CFast|InnoDisk Corp\\. - mSATA|Mini PCIeDOM|mSATA( mini)?|" "(2.5\" SATA SSD|CFast|Mini PCIeDOM|(InnoDisk Corp\\. - )?mSATA( mini)?) (1IE3|3[IM]E[34])( V2)?|"
"M\\.2 \\(S42\\)|SATA Slim|SATADOM-[MS][HLV]( Type [CD])?) (1IE3|3[IM]E[34])( V2)?", "(M\\.2 \\(S42\\)|SATA Slim|SATADOM-[MS][HLV]( Type [CD])?) (1IE3|3[IM]E[34])( V2)?",
"", "", "", "",
//"-v 1,raw48,Raw_Read_Error_Rate " //"-v 1,raw48,Raw_Read_Error_Rate "
//"-v 2,raw48,Throughput_Performance " //"-v 2,raw48,Throughput_Performance "
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment