From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: qemu-devel@nongnu.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com> Subject: [PATCH v3 RESEND 0/3] nvram: at24c: fix problems related to "rom-size" Date: Sun, 20 May 2018 09:00:34 +0200 [thread overview] Message-ID: <20180520070037.8593-1-wsa+renesas@sang-engineering.com> (raw) I used this driver as a template for a custom one. While hacking on my own, I noticed some problems in this driver, too. This series fixes the first set of them, related to the "rom-size" parameter. It fixes a segfault. I think the first patch is clearly suitable for stable. I think the second one, too, but not as clearly. The third one is a cleanup and not for stable. Still, I am open for opinions about these thoughts. Thanks, Wolfram This is the same v3 as last time. Rebased to current master, but that produced no diff. Changes since v2: * removed '\n' from error_report-strings * made sure checkpatch is happy * added tags from Philippe (thanks!) Changes since v1: * reordered patches according to significance for stable * use AT24C_ROMSIZE_DEFAULT instead of magic value * patch 3 doesn't improve the ERR macro anymore but replaces it completely with error_report(). Wolfram Sang (3): nvram: at24c: prevent segfault by checking "rom-size" nvram: at24c: use a sane default for "rom-size" nvram: at24c: use standard error reporting hw/nvram/eeprom_at24c.c | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) -- 2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: qemu-devel@nongnu.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com> Subject: [Qemu-devel] [PATCH v3 RESEND 0/3] nvram: at24c: fix problems related to "rom-size" Date: Sun, 20 May 2018 09:00:34 +0200 [thread overview] Message-ID: <20180520070037.8593-1-wsa+renesas@sang-engineering.com> (raw) I used this driver as a template for a custom one. While hacking on my own, I noticed some problems in this driver, too. This series fixes the first set of them, related to the "rom-size" parameter. It fixes a segfault. I think the first patch is clearly suitable for stable. I think the second one, too, but not as clearly. The third one is a cleanup and not for stable. Still, I am open for opinions about these thoughts. Thanks, Wolfram This is the same v3 as last time. Rebased to current master, but that produced no diff. Changes since v2: * removed '\n' from error_report-strings * made sure checkpatch is happy * added tags from Philippe (thanks!) Changes since v1: * reordered patches according to significance for stable * use AT24C_ROMSIZE_DEFAULT instead of magic value * patch 3 doesn't improve the ERR macro anymore but replaces it completely with error_report(). Wolfram Sang (3): nvram: at24c: prevent segfault by checking "rom-size" nvram: at24c: use a sane default for "rom-size" nvram: at24c: use standard error reporting hw/nvram/eeprom_at24c.c | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) -- 2.11.0
next reply other threads:[~2018-05-20 7:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-20 7:00 Wolfram Sang [this message] 2018-05-20 7:00 ` [Qemu-devel] [PATCH v3 RESEND 0/3] nvram: at24c: fix problems related to "rom-size" Wolfram Sang 2018-05-20 7:00 ` [PATCH v3 RESEND 1/3] nvram: at24c: prevent segfault by checking "rom-size" Wolfram Sang 2018-05-20 7:00 ` [Qemu-devel] " Wolfram Sang 2018-05-20 7:00 ` [PATCH v3 RESEND 2/3] nvram: at24c: use a sane default for "rom-size" Wolfram Sang 2018-05-20 7:00 ` [Qemu-devel] " Wolfram Sang 2018-05-20 7:00 ` [PATCH v3 RESEND 3/3] nvram: at24c: use standard error reporting Wolfram Sang 2018-05-20 7:00 ` [Qemu-devel] " Wolfram Sang 2018-05-20 13:27 ` Peter Maydell
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=20180520070037.8593-1-wsa+renesas@sang-engineering.com \ --to=wsa+renesas@sang-engineering.com \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=qemu-devel@nongnu.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: linkBe 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.