From: Ashok Raj <ashok.raj@intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.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>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH 1/1] platform/x86/intel/ifs: Remove unnecessary ret init
Date: Thu, 25 Jan 2024 08:26:18 -0800 [thread overview]
Message-ID: <ZbKLqgte4rVx8yGx@a4bf019067fa.jf.intel.com> (raw)
In-Reply-To: <b9368410-e084-8d4e-1c81-55c4e6a22434@linux.intel.com>
On Thu, Jan 25, 2024 at 06:12:00PM +0200, Ilpo Järvinen wrote:
> On Thu, 25 Jan 2024, Ashok Raj wrote:
>
[snip]
>
> 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 don't have anything beyond this that conflicts with this change.
Feel free to add
Reviewed-by: Ashok Raj <ashok.raj@intel.com>
next prev parent reply other threads:[~2024-01-25 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 13:03 Ilpo Järvinen
2024-01-25 15:21 ` Ashok Raj
2024-01-25 16:12 ` Ilpo Järvinen
2024-01-25 16:26 ` Ashok Raj [this message]
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=ZbKLqgte4rVx8yGx@a4bf019067fa.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.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
all inboxes | Powered by JetHome®