Messages in this thread | | | Date | Mon, 19 May 2008 23:47:18 +0200 | From | "Jesper Juhl" <> | Subject | Re: [PATCH] fix typo "thier" -> "their" |
| |
Hi Uwe,
I've applied the first drivers/base/sys.c part of the patch to the Trivial tree. The drivers/pnp/manager.c bit no longer applies.
/Jesper Juhl
2008/4/2 Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>: > Signed-off-by: Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com> > Cc: trivial@kernel.org > --- > drivers/base/sys.c | 2 +- > drivers/pnp/manager.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/base/sys.c b/drivers/base/sys.c > index 8e13fd9..84be616 100644 > --- a/drivers/base/sys.c > +++ b/drivers/base/sys.c > @@ -283,7 +283,7 @@ void sysdev_unregister(struct sys_device * sysdev) > * and the class driver. > * > * Note: The list is iterated in reverse order, so that we shut down > - * child devices before we shut down thier parents. The list ordering > + * child devices before we shut down their parents. The list ordering > * is guaranteed by virtue of the fact that child devices are registered > * after their parents. > */ > diff --git a/drivers/pnp/manager.c b/drivers/pnp/manager.c > index c28caf2..745a668 100644 > --- a/drivers/pnp/manager.c > +++ b/drivers/pnp/manager.c > @@ -382,7 +382,7 @@ fail: > * @res: pointer to the new resource config > * @mode: 0 or PNP_CONFIG_FORCE > * > - * This function can be used by drivers that want to manually set thier resources. > + * This function can be used by drivers that want to manually set their resources. > */ > int pnp_manual_config_dev(struct pnp_dev *dev, struct pnp_resource_table *res, > int mode) > -- > 1.5.4.5 > >
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |