From: Johannes Krottmayer <krjdev@gmail.com>
To: u-boot@lists.denx.de
Cc: Johannes Krottmayer <krjdev@gmail.com>
Subject: [PATCH 0/2] Fix doc path in warning message
Date: Tue, 1 Mar 2022 04:49:49 +0100 [thread overview]
Message-ID: <20220301034950.30849-1-krjdev@gmail.com> (raw)
Fix doc path in warning messages.
Okay?
Johannes Krottmayer (2):
Makefile: Fix doc path in warning message
tools: buildman: Fix doc path in warning message
Makefile | 4 ++--
tools/buildman/test.py | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-01 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 3:49 Johannes Krottmayer [this message]
2022-03-01 3:49 ` [PATCH 1/2] Makefile: Fix doc path in warning message Johannes Krottmayer
2022-03-01 3:49 ` [PATCH 2/2] tools: buildman: " Johannes Krottmayer
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=20220301034950.30849-1-krjdev@gmail.com \
--to=krjdev@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.