All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreenidhi Shedi <yesshedi@gmail.com>
To: grub-devel@gnu.org
Cc: yesshedi@gmail.com, alexey.makhalov@broadcom.com,
	daniel.kiper@oracle.com
Subject: [PATCH v1 0/2] Fix cfg file parsing and command line parsing
Date: Sun, 18 May 2025 13:21:19 +0530	[thread overview]
Message-ID: <20250518075121.76584-1-yesshedi@gmail.com> (raw)

Hi GRUB Developers,

This patch series contains two fixes to improve how GRUB handles
environment files and constructs the kernel command line, these issues
were reported by PhotonOS customers.

The first patch ensures that empty lines in environment files are
skipped during parsing.

The second patch removes unnecessary escaping of quotes in the
constructed command line, as the Linux kernel does not support escaped
quotes.

Thanks for your time and consideration.

v0 changes:
- Initial revision.
- https://lists.gnu.org/archive/html/grub-devel/2025-05/msg00085.html

v1 changes:
- Added cover leter
- Improved commit message as suggested by Daniel Kiper

--
Shreenidhi Shedi

--
2.49.0

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

             reply	other threads:[~2025-05-18  8:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18  7:51 Shreenidhi Shedi [this message]
2025-05-18  7:51 ` [PATCH v1 1/2] envblk: ignore empty new lines while parsing env files Shreenidhi Shedi
2025-05-19 17:13   ` Daniel Kiper
2025-05-19 17:25     ` Alexey Makhalov via Grub-devel
2025-05-19 18:20     ` Shreenidhi Shedi
2025-05-19 18:17   ` Vladimir 'phcoder' Serbinenko
2025-05-18  7:51 ` [PATCH v1 2/2] cmdline: fix command line parsing in grub Shreenidhi Shedi

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=20250518075121.76584-1-yesshedi@gmail.com \
    --to=yesshedi@gmail.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=daniel.kiper@oracle.com \
    --cc=grub-devel@gnu.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 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.