sched/deadline: Fix typo "a entity" to "an entity" in comment
PATCH 1/1 sched/deadline: Fix typo "a entity" to "an entity" in comment
Corrected a grammatical mistake in the comment of deadline.c, changing "a entity" to "an entity" to conform with proper English usage.
Signed-off-by Shou-Chi Chen <[email protected]>
--- kernel/sched/deadline.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
kernel/sched/deadline.c +4 -4
@@ -848,20 +848,20 @@ static bool dl_entity_overflow(struct sched_dl_entity *dl_se, u64 t);/* * Pure Earliest Deadline First (EDF) scheduling does not deal with the -* possibility of a entity lasting more than what it declared, and thus +* possibility of an entity lasting more than what it declared, and thus * exhausting its runtime. * * Here we are interested in making runtime overrun possible, but we do -* not want a entity which is misbehaving to affect the scheduling of all +* not want an entity which is misbehaving to affect the scheduling of all * other entities. * Therefore, a budgeting strategy called Constant Bandwidth Server (CBS) * is used, in order to confine each entity within its own bandwidth. * * This function deals exactly with that, and ensures that when the runtime -* of a entity is replenished, its deadline is also postponed. That ensures +* of an entity is replenished, its deadline is also postponed. That ensures * the overrunning entity can't interfere with other entity in the system and * can't make them miss their deadlines. Reasons why this kind of overruns -* could happen are, typically, a entity voluntarily trying to overcome its +* could happen are, typically, an entity voluntarily trying to overcome its * runtime, or it just underestimated it during sched_setattr(). */ static void replenish_dl_entity (struct sched_dl_entity *dl_se)
Signature · 1 line
2.43.0