util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin English <austinenglish@gmail.com>
To: util-linux@vger.kernel.org
Cc: Austin English <austinenglish@gmail.com>
Subject: [PATCH 2/6] libmount/src/utils.c: fix "maybe be" duplication
Date: Mon, 13 May 2019 13:53:15 -0500	[thread overview]
Message-ID: <20190513185319.28853-2-austinenglish@gmail.com> (raw)
In-Reply-To: <20190513185319.28853-1-austinenglish@gmail.com>

Signed-off-by: Austin English <austinenglish@gmail.com>
---
 libmount/src/utils.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libmount/src/utils.c b/libmount/src/utils.c
index 7f6cc1405..73166cb91 100644
--- a/libmount/src/utils.c
+++ b/libmount/src/utils.c
@@ -913,7 +913,7 @@ int mnt_open_uniq_filename(const char *filename, char **name)
  * should be canonicalized. The returned pointer should be freed by the caller.
  *
  * WARNING: the function compares st_dev of the @path elements. This traditional
- * way maybe be insufficient on filesystems like Linux "overlay". See also
+ * way may be insufficient on filesystems like Linux "overlay". See also
  * mnt_table_find_target().
  *
  * Returns: allocated string with the target of the mounted device or NULL on error
-- 
2.21.0


  reply	other threads:[~2019-05-13 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 18:53 [PATCH 1/6] lib/colors.c: fix "maybe be" duplication Austin English
2019-05-13 18:53 ` Austin English [this message]
2019-05-13 18:53 ` [PATCH 3/6] misc-utils/lsblk.8: " Austin English
2019-05-13 18:53 ` [PATCH 4/6] sys-utils/mount.8: " Austin English
2019-05-13 18:53 ` [PATCH 5/6] sys-utils/rtcwake.8.in: " Austin English
2019-05-13 18:53 ` [PATCH 6/6] text-utils/column.1: " Austin English
2019-05-15 11:50 ` [PATCH 1/6] lib/colors.c: " Karel Zak

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=20190513185319.28853-2-austinenglish@gmail.com \
    --to=austinenglish@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).