From: Hans de Goede <hdegoede@redhat.com>
To: Jorge Lopez <jorgealtxwork@gmail.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas@t-8ch.de,
ilpo.jarvinen@linux.intel.com, dan.carpenter@linaro.org
Subject: Re: [PATCH 0/8] hp-bioscfg: Overall fixes and code cleanup
Date: Mon, 7 Aug 2023 13:38:33 +0200 [thread overview]
Message-ID: <92096817-0183-566a-cdd3-74e6fa3a09c8@redhat.com> (raw)
In-Reply-To: <20230731203141.30044-1-jorge.lopez2@hp.com>
Hi,
On 7/31/23 22:31, Jorge Lopez wrote:
> Submit individual patches to address memory leaks and uninitialized
> variable errors.
> Addressed several review comments making the source code more readable.
> Removed duplicate use of variable in inner loop.
>
> Changes were tested with a HP EliteBook x360 1030 G3
>
> Jorge Lopez (8):
> hp-bioscfg: Fix memory leaks in attribute packages
> hp-bioscfg: Fix uninitialized variable errors
> hp-bioscfg: Replace the word HACK from source code
> hp-bioscfg: Change how prerequisites size is evaluated
> hp-bioscfg: Change how order list size is evaluated
> hp-bioscfg: Change how enum possible values size is evaluated
> hp-bioscfg: Change how password encoding size is evaluated
> hp-bioscfg: Remove duplicate use of variable in inner loop
>
> .../x86/hp/hp-bioscfg/enum-attributes.c | 24 ++++++++----
> .../x86/hp/hp-bioscfg/int-attributes.c | 15 +++++--
> .../x86/hp/hp-bioscfg/order-list-attributes.c | 39 ++++++++++++-------
> .../x86/hp/hp-bioscfg/passwdobj-attributes.c | 27 +++++++++----
> .../x86/hp/hp-bioscfg/string-attributes.c | 13 +++++--
> 5 files changed, 82 insertions(+), 36 deletions(-)
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
prev parent reply other threads:[~2023-08-07 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 20:31 Jorge Lopez
2023-07-31 20:31 ` [PATCH 1/8] hp-bioscfg: Fix memory leaks in attribute packages Jorge Lopez
2023-07-31 20:31 ` [PATCH 2/8] hp-bioscfg: Fix uninitialized variable errors Jorge Lopez
2023-07-31 20:31 ` [PATCH 3/8] hp-bioscfg: Replace the word HACK from source code Jorge Lopez
2023-07-31 20:31 ` [PATCH 4/8] hp-bioscfg: Change how prerequisites size is evaluated Jorge Lopez
2023-07-31 20:31 ` [PATCH 5/8] hp-bioscfg: Change how order list " Jorge Lopez
2023-07-31 20:31 ` [PATCH 6/8] hp-bioscfg: Change how enum possible values " Jorge Lopez
2023-07-31 20:31 ` [PATCH 7/8] hp-bioscfg: Change how password encoding " Jorge Lopez
2023-07-31 20:31 ` [PATCH 8/8] hp-bioscfg: Remove duplicate use of variable in inner loop Jorge Lopez
2023-08-01 13:35 ` [PATCH 0/8] hp-bioscfg: Overall fixes and code cleanup Dan Carpenter
2023-08-01 14:52 ` Jorge Lopez
2023-08-01 15:04 ` Dan Carpenter
2023-08-01 15:10 ` Jorge Lopez
2023-08-01 15:36 ` Dan Carpenter
2023-08-07 11:38 ` Hans de Goede [this message]
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=92096817-0183-566a-cdd3-74e6fa3a09c8@redhat.com \
--to=hdegoede@redhat.com \
--cc=dan.carpenter@linaro.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jorgealtxwork@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thomas@t-8ch.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
all inboxes | Powered by JetHome®