Messages in this thread | | | Date | Sun, 20 Jan 2019 22:45:27 +0100 | From | Sebastian Reichel <> | Subject | Re: [PATCH] power: supply: charger-manager: Fix trivial language typos |
| |
Hi,
On Tue, Jan 08, 2019 at 01:12:12PM +0100, Krzysztof Kozlowski wrote: > Fix few trivial language typos. > > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> > ---
Thanks, queued.
-- Sebastian
> drivers/power/supply/charger-manager.c | 18 +++++++++--------- > 1 file changed, 9 insertions(+), 9 deletions(-) > > diff --git a/drivers/power/supply/charger-manager.c b/drivers/power/supply/charger-manager.c > index 38be91f21cc4..2e8db5e6de0b 100644 > --- a/drivers/power/supply/charger-manager.c > +++ b/drivers/power/supply/charger-manager.c > @@ -4,7 +4,7 @@ > * > * This driver enables to monitor battery health and control charger > * during suspend-to-mem. > - * Charger manager depends on other devices. register this later than > + * Charger manager depends on other devices. Register this later than > * the depending devices. > * > * This program is free software; you can redistribute it and/or modify > @@ -29,7 +29,7 @@ > #include <linux/thermal.h> > > /* > - * Default termperature threshold for charging. > + * Default temperature threshold for charging. > * Every temperature units are in tenth of centigrade. > */ > #define CM_DEFAULT_RECHARGE_TEMP_DIFF 50 > @@ -356,7 +356,7 @@ static bool is_polling_required(struct charger_manager *cm) > * Note that Charger Manager keeps the charger enabled regardless whether > * the charger is charging or not (because battery is full or no external > * power source exists) except when CM needs to disable chargers forcibly > - * bacause of emergency causes; when the battery is overheated or too cold. > + * because of emergency causes; when the battery is overheated or too cold. > */ > static int try_charger_enable(struct charger_manager *cm, bool enable) > { > @@ -643,7 +643,7 @@ static int cm_check_thermal_status(struct charger_manager *cm) > if (ret) { > /* FIXME: > * No information of battery temperature might > - * occur hazadous result. We have to handle it > + * occur hazardous result. We have to handle it > * depending on battery type. > */ > dev_err(cm->dev, "Failed to get battery temperature\n"); > @@ -693,7 +693,7 @@ static bool _cm_monitor(struct charger_manager *cm) > uevent_notify(cm, default_event_names[temp_alrt]); > > /* > - * Check whole charging duration and discharing duration > + * Check whole charging duration and discharging duration > * after full-batt. > */ > } else if (!cm->emergency_stop && check_charging_duration(cm)) { > @@ -866,7 +866,7 @@ static void battout_handler(struct charger_manager *cm) > } > > /** > - * misc_event_handler - Handler for other evnets > + * misc_event_handler - Handler for other events > * @cm: the Charger Manager representing the battery. > * @type: the Charger Manager representing the battery. > */ > @@ -1218,7 +1218,7 @@ static int charger_extcon_init(struct charger_manager *cm, > } > > /** > - * charger_manager_register_extcon - Register extcon device to recevie state > + * charger_manager_register_extcon - Register extcon device to receive state > * of charger cable. > * @cm: the Charger Manager representing the battery. > * > @@ -1538,7 +1538,7 @@ static struct charger_desc *of_cm_parse_desc(struct device *dev) > of_property_read_u32(np, "cm-discharging-max", > &desc->discharging_max_duration_ms); > > - /* battery charger regualtors */ > + /* battery charger regulators */ > desc->num_charger_regulators = of_get_child_count(np); > if (desc->num_charger_regulators) { > struct charger_regulator *chg_regs; > @@ -1801,7 +1801,7 @@ static int charger_manager_probe(struct platform_device *pdev) > > /* > * Charger-manager have to check the charging state right after > - * tialization of charger-manager and then update current charging > + * initialization of charger-manager and then update current charging > * state. > */ > cm_monitor(); > -- > 2.7.4 > [unhandled content-type:application/pgp-signature] | |