From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] xilinx: fru: Small update and fixes
Date: Tue, 10 Nov 2020 13:21:32 +0100 [thread overview]
Message-ID: <cover.1605010893.git.michal.simek@xilinx.com> (raw)
Hi,
I am sending 3 more patches for fru code. Especially the second patch is
important because it ensures that data in .data section is not overwritten
based on parsed structures.
Thanks,
Michal
Michal Simek (3):
fru: common: Switch capture variable with the rest
fru: ops: Do not let parser to write data to not allocated space
fru: common: Record pcie/uuid fields in custom board area
board/xilinx/common/fru.h | 6 +++++-
board/xilinx/common/fru_ops.c | 10 ++++++++--
2 files changed, 13 insertions(+), 3 deletions(-)
--
2.29.2
next reply other threads:[~2020-11-10 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 12:21 Michal Simek [this message]
2020-11-10 12:21 ` [PATCH 1/3] fru: common: Switch capture variable with the rest Michal Simek
2020-11-10 12:21 ` [PATCH 2/3] fru: ops: Do not let parser to write data to not allocated space Michal Simek
2020-11-10 12:21 ` [PATCH 3/3] fru: common: Record pcie/uuid fields in custom board area Michal Simek
2020-11-20 9:49 ` [PATCH 0/3] xilinx: fru: Small update and fixes Michal Simek
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=cover.1605010893.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox