From: Stephen Hemminger <stephen@networkplumber.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: netdev@vger.kernel.org, valex@mellanox.com, jiri@resnulli.us
Subject: Re: [PATCH 2/2] doc: fix typo of snapshot in documentation
Date: Thu, 9 Jan 2020 12:36:38 -0800 [thread overview]
Message-ID: <20200109123638.6dc0a155@hermes.lan> (raw)
In-Reply-To: <f1b34465-0bdc-e108-c887-5d04ec64e861@intel.com>
On Thu, 9 Jan 2020 12:11:36 -0800
Jacob Keller <jacob.e.keller@intel.com> wrote:
> On 1/9/2020 12:06 PM, Jacob Keller wrote:
> > On 1/9/2020 12:00 PM, Stephen Hemminger wrote:
> >> On Thu, 9 Jan 2020 11:08:21 -0800
> >> Jacob Keller <jacob.e.keller@intel.com> wrote:
> >>
> >>> A couple of locations accidentally misspelled snapshot as shapshot.
> >>>
> >>> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> >>> ---
> >>> Documentation/admin-guide/devices.txt | 2 +-
> >>> Documentation/media/v4l-drivers/meye.rst | 2 +-
> >>> 2 files changed, 2 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/Documentation/admin-guide/devices.txt b/Documentation/admin-guide/devices.txt
> >>> index 1c5d2281efc9..2a97aaec8b12 100644
> >>> --- a/Documentation/admin-guide/devices.txt
> >>> +++ b/Documentation/admin-guide/devices.txt
> >>> @@ -319,7 +319,7 @@
> >>> 182 = /dev/perfctr Performance-monitoring counters
> >>> 183 = /dev/hwrng Generic random number generator
> >>> 184 = /dev/cpu/microcode CPU microcode update interface
> >>> - 186 = /dev/atomicps Atomic shapshot of process state data
> >>> + 186 = /dev/atomicps Atomic snapshot of process state data
> >>> 187 = /dev/irnet IrNET device
> >>
> >> Oops, irnet is part of irda which is no longer part of the kernel.
> >>
> >
> > This is probably based on the wrong tree. Will rebase and re-send.
> >
> > Thanks,
> > Jake>
>
> Well, I did rebase the patches locally but the contents are still the
> same so I'm not going to resend. I guess it's just because the
> devices.txt file hasn't been updated?
>
> -Jake
Yes, it looks like references to irnet were never deleted.
next prev parent reply other threads:[~2020-01-09 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 19:08 [PATCH 1/2] devlink: correct misspelling of snapshot Jacob Keller
2020-01-09 19:08 ` [PATCH 2/2] doc: fix typo of snapshot in documentation Jacob Keller
2020-01-09 20:00 ` Stephen Hemminger
2020-01-09 20:06 ` Jacob Keller
2020-01-09 20:11 ` Jacob Keller
2020-01-09 20:36 ` Stephen Hemminger [this message]
2020-01-11 0:49 ` David Miller
2020-01-10 9:36 ` [PATCH 1/2] devlink: correct misspelling of snapshot Jiri Pirko
2020-01-10 17:47 ` Jacob Keller
2020-01-11 0:49 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200109123638.6dc0a155@hermes.lan \
--to=stephen@networkplumber.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=valex@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox