Platform-driver-x86 archive mirror
 help / color / mirror / Atom feed
From: "Fradella, Ben" <Ben.Fradella@netapp.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
	"bcfradella@proton.me" <bcfradella@proton.me>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Ranjan Dutta <ranjan.dutta@intel.com>,
	Yifan2 Li <yifan2.li@intel.com>,
	Jonathan Yong <jonathan.yong@intel.com>
Subject: Re: [PATCH] p2sb: Don't init until unassigned resources have been assigned.
Date: Mon, 13 May 2024 15:53:27 +0000	[thread overview]
Message-ID: <MW5PR06MB893057D6D58E498EBE16A8B0F9E22@MW5PR06MB8930.namprd06.prod.outlook.com> (raw)
In-Reply-To: <7867b308-7cea-4282-82e8-551d88fe70c4@redhat.com>

> On 2024-05-13 07:03, hdegoede@redhat.com wrote:
>
> Thank you for your patch, I've applied this patch 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

Thank you!

      reply	other threads:[~2024-05-13 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 16:49 [PATCH] p2sb: Don't init until unassigned resources have been assigned bcfradella
2024-05-09 17:04 ` Lukas Wunner
2024-05-10 14:50   ` Andy Shevchenko
2024-05-10 19:22     ` Klara Modin
2024-05-12 10:23       ` Shinichiro Kawasaki
2024-05-13 12:03 ` Hans de Goede
2024-05-13 15:53   ` Fradella, Ben [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=MW5PR06MB893057D6D58E498EBE16A8B0F9E22@MW5PR06MB8930.namprd06.prod.outlook.com \
    --to=ben.fradella@netapp.com \
    --cc=bcfradella@proton.me \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jonathan.yong@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=ranjan.dutta@intel.com \
    --cc=yifan2.li@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).