From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Jithu Joseph <jithu.joseph@intel.com>,
Tony Luck <tony.luck@intel.com>,
Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] platform/x86/intel/ifs: Remove unnecessary ret init
Date: Thu, 25 Jan 2024 18:12:00 +0200 (EET) [thread overview]
Message-ID: <b9368410-e084-8d4e-1c81-55c4e6a22434@linux.intel.com> (raw)
In-Reply-To: <ZbJ8gp47CWDDqCb4@a4bf019067fa.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
On Thu, 25 Jan 2024, Ashok Raj wrote:
> Hi Ilpo
>
> thanks for looking into it.
>
> On Thu, Jan 25, 2024 at 03:03:28PM +0200, Ilpo Järvinen wrote:
> > ret variable is assigned unconditionally in ifs_load_firmware(), thus
> > remove the unnecessary initialization of it.
> >
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > ---
> > drivers/platform/x86/intel/ifs/load.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/platform/x86/intel/ifs/load.c b/drivers/platform/x86/intel/ifs/load.c
> > index a1ee1a74fc3c..03e49b836a6b 100644
> > --- a/drivers/platform/x86/intel/ifs/load.c
> > +++ b/drivers/platform/x86/intel/ifs/load.c
> > @@ -383,7 +383,7 @@ int ifs_load_firmware(struct device *dev)
> > unsigned int expected_size;
> > const struct firmware *fw;
> > char scan_path[64];
> > - int ret = -EINVAL;
> > + int ret;
> >
>
> Looks reasonable to me.
>
> I can keep this as a separate cleanup patch, or merge the change in this
> patch.
>
> What ever Hans/You prefer.
Hi,
I was thinking of merging it myself into pdx86 review-ilpo -> next after
allowing it sit on the queue a day or two. IMO, doesn't need to be more
complicated than the usual process kernel process with patches, it would
just take extra time from all the more there are middlemens handling the
patch (after all this is just a trivial cleanup which I noticed while
reviewing the patches you sent and since it didn't conflict the series,
I just sent the obvious cleanup).
But that's assuming you don't have anything conflicting beyond those
patches which you sent? If that's the case, it would be better for you to
take care of it so just let me and I won't merge it myself until it comes
back.
--
i.
next prev parent reply other threads:[~2024-01-25 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:03 [PATCH 1/1] platform/x86/intel/ifs: Remove unnecessary ret init Ilpo Järvinen
2024-01-25 15:21 ` Ashok Raj
2024-01-25 16:12 ` Ilpo Järvinen [this message]
2024-01-25 16:26 ` Ashok Raj
2024-01-31 10:28 ` Ilpo Järvinen
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=b9368410-e084-8d4e-1c81-55c4e6a22434@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=hdegoede@redhat.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tony.luck@intel.com \
/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