The DVB term can either refer to the subsystem or to a delivery system. Avoid it in the first case at the kernel-doc markups.
Showing the changes to include/uapi/linux (1 of 1 file). Show all
Unified · Split
| @@ -239,11 +239,11 @@ enum fe_sec_mini_cmd { · 238 unmodified lines | ||
| 239 | 239 | * @FE_NONE: The frontend doesn't have any kind of lock. |
| 240 | 240 | * That's the initial frontend status |
| 241 | 241 | * @FE_HAS_SIGNAL: Has found something above the noise level. |
| 242 | − * @FE_HAS_CARRIER: Has found a DVB signal. | |
| 242 | + * @FE_HAS_CARRIER: Has found a signal. | |
| 243 | 243 | * @FE_HAS_VITERBI: FEC inner coding (Viterbi, LDPC or other inner code). |
| 244 | 244 | * is stable. |
| 245 | 245 | * @FE_HAS_SYNC: Synchronization bytes was found. |
| 246 | − * @FE_HAS_LOCK: DVB were locked and everything is working. | |
| 246 | + * @FE_HAS_LOCK: Digital TV were locked and everything is working. | |
| 247 | 247 | * @FE_TIMEDOUT: Fo lock within the last about 2 seconds. |
| 248 | 248 | * @FE_REINIT: Frontend was reinitialized, application is recommended |
| 249 | 249 | * to reset DiSEqC, tone and parameters. |
| @@ -269,7 +269,7 @@ enum fe_status { · 19 unmodified lines | ||
| 269 | 269 | * This parameter indicates if spectral inversion should be presumed or |
| 270 | 270 | * not. In the automatic setting (``INVERSION_AUTO``) the hardware will try |
| 271 | 271 | * to figure out the correct setting by itself. If the hardware doesn't |
| 272 | − * support, the DVB core will try to lock at the carrier first with | |
| 272 | + * support, the %dvb_frontend will try to lock at the carrier first with | |
| 273 | 273 | * inversion off. If it fails, it will try to enable inversion. |
| 274 | 274 | */ |
| 275 | 275 | enum fe_spectral_inversion { |