| Message ID | mailman.790.1640703116.993.libcamera-devel@lists.libcamera.org |
|---|---|
| State | Accepted |
| Commit | 030e6f389e2d0fa3f10a47634f3609378ccaf70e |
| Headers | show |
| Series |
|
| Related | show |
Hello Eugen On Tue, Dec 28, 2021 at 04:51:43PM +0200, Eugen Hristev via libcamera-devel wrote: > Date: Tue, 28 Dec 2021 16:51:43 +0200 > From: Eugen Hristev <eugen.hristev@microchip.com> > To: libcamera-devel@lists.libcamera.org > Subject: [PATCH] Documentation: guides: introduction: fix typos > X-Mailer: git-send-email 2.25.1 > > Fix typos. > > Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org> Thanks j > --- > > Found during reading. > Last line is unchanged, but Git puts it in the patch due to missing newline > at end of file. > > > Documentation/guides/introduction.rst | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/Documentation/guides/introduction.rst b/Documentation/guides/introduction.rst > index d3a42a23..e2091797 100644 > --- a/Documentation/guides/introduction.rst > +++ b/Documentation/guides/introduction.rst > @@ -17,7 +17,7 @@ by vendors without a common architecture or API for application developers. > > libcamera provides a complete camera stack for Linux based systems to abstract > functionality desired by camera application developers and process the > -configuration of hardware and image control algorithms requried to obtain > +configuration of hardware and image control algorithms required to obtain > desireable results from the camera. > > .. _Video for Linux 2: https://www.linuxtv.org/downloads/v4l-dvb-apis-new/userspace-api/v4l/v4l2.html > @@ -152,9 +152,9 @@ Architecture > While offering a unified API towards upper layers, and presenting itself as a > single library, libcamera isn’t monolithic. It exposes multiple components > through its public API and is built around a set of separate helpers internally. > -Hardware abstractractions are handled through the use of device-specific > -components where required and dynamically loadable plugins are used to separate > -image processing algorithms from the core libcamera codebase. > +Hardware abstractions are handled through the use of device-specific components > +where required and dynamically loadable plugins are used to separate image > +processing algorithms from the core libcamera codebase. > > :: > > @@ -316,4 +316,4 @@ Applications which link dynamically against libcamera and use only the public > API are an independent work of the authors and have no license restrictions > imposed upon them from libcamera. > > -.. _LGPL-2.1-or-later: https://spdx.org/licenses/LGPL-2.1-or-later.html > \ No newline at end of file > +.. _LGPL-2.1-or-later: https://spdx.org/licenses/LGPL-2.1-or-later.html > -- > 2.25.1 >
diff --git a/Documentation/guides/introduction.rst b/Documentation/guides/introduction.rst index d3a42a23..e2091797 100644 --- a/Documentation/guides/introduction.rst +++ b/Documentation/guides/introduction.rst @@ -17,7 +17,7 @@ by vendors without a common architecture or API for application developers. libcamera provides a complete camera stack for Linux based systems to abstract functionality desired by camera application developers and process the -configuration of hardware and image control algorithms requried to obtain +configuration of hardware and image control algorithms required to obtain desireable results from the camera. .. _Video for Linux 2: https://www.linuxtv.org/downloads/v4l-dvb-apis-new/userspace-api/v4l/v4l2.html @@ -152,9 +152,9 @@ Architecture While offering a unified API towards upper layers, and presenting itself as a single library, libcamera isn’t monolithic. It exposes multiple components through its public API and is built around a set of separate helpers internally. -Hardware abstractractions are handled through the use of device-specific -components where required and dynamically loadable plugins are used to separate -image processing algorithms from the core libcamera codebase. +Hardware abstractions are handled through the use of device-specific components +where required and dynamically loadable plugins are used to separate image +processing algorithms from the core libcamera codebase. :: @@ -316,4 +316,4 @@ Applications which link dynamically against libcamera and use only the public API are an independent work of the authors and have no license restrictions imposed upon them from libcamera. -.. _LGPL-2.1-or-later: https://spdx.org/licenses/LGPL-2.1-or-later.html \ No newline at end of file +.. _LGPL-2.1-or-later: https://spdx.org/licenses/LGPL-2.1-or-later.html
Fix typos. Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com> --- Found during reading. Last line is unchanged, but Git puts it in the patch due to missing newline at end of file. Documentation/guides/introduction.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)