All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>,
	Ivan Mikhaylov <ivan.mikhaylov@siemens.com>
Subject: [PATCH 2/3] mkimage: Drop unused OPT_STRING constant
Date: Thu, 25 Nov 2021 20:03:03 +0100	[thread overview]
Message-ID: <bbd84f84e89072c22c9b82b136709a7e476dad9d.1637866984.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1637866984.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

The actual opt string is inlined - and different. Seems this was a
left-over from older versions of 603e26f76346.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 tools/mkimage.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/tools/mkimage.c b/tools/mkimage.c
index fbe883ce36..a4844d0f18 100644
--- a/tools/mkimage.c
+++ b/tools/mkimage.c
@@ -146,7 +146,6 @@ static int add_content(int type, const char *fname)
 	return 0;
 }
 
-#define OPT_STRING "a:A:b:B:c:C:d:D:e:Ef:Fk:i:K:ln:N:p:O:rR:qstT:vVx"
 static void process_args(int argc, char **argv)
 {
 	char *ptr;
-- 
2.31.1


  parent reply	other threads:[~2021-11-25 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 19:03 [PATCH 0/3] mkimage: allow to specify signing algorithm Jan Kiszka
2021-11-25 19:03 ` [PATCH 1/3] image-fit: Make string of algo parameter constant Jan Kiszka
2021-11-25 19:03 ` Jan Kiszka [this message]
2021-11-25 19:03 ` [PATCH 3/3] mkimage: Allow to specify the signature algorithm on the command line Jan Kiszka
2022-01-13 12:38 ` [PATCH 0/3] mkimage: allow to specify signing algorithm Jan Kiszka
2022-01-13 13:40   ` Simon Glass
2022-01-13 23:28   ` Dhananjay Phadke
2022-01-14  9:21     ` Jan Kiszka

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=bbd84f84e89072c22c9b82b136709a7e476dad9d.1637866984.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ivan.mikhaylov@siemens.com \
    --cc=sjg@chromium.org \
    --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.