X86 platform drivers
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Hans de Goede" <hdegoede@redhat.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Ma Jun" <Jun.Ma2@amd.com>,
	"Limonciello, Mario" <Mario.Limonciello@amd.com>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [GIT PULL] mmutable branch between pdx86 amd wbrf branch and wifi / amdgpu due for the v6.8 merge window
Date: Mon, 11 Dec 2023 12:41:42 +0100	[thread overview]
Message-ID: <5e14be1fc61d9d7027cd50f4148eea52e40fb9d3.camel@sipsolutions.net> (raw)
In-Reply-To: <6395b87b-7cb6-4412-b6e5-e6075353fb6d@redhat.com>

Hi,

> Here is a pull-request for the platform-drivers-x86 parts of:
> 
> https://lore.kernel.org/platform-driver-x86/20231211100630.2170152-1-Jun.Ma2@amd.com/
> 
> From my pov the pdx86 bits are ready and the platform-drivers-x86-amd-wbrf-v6.8-1 tag can be merged by you to merge the wifi-subsys resp. the amdgpu driver changes on top.
> 
> This only adds kernel internal API, so if in the future the API needs work that can be done.

I've been fine with the wifi bits since around v3 of the patchset ;-)

So the idea is that I'll pull this into wireless-next and then apply the
two wireless patches on top, right?

AFAICT, since the other patches don't depend on wireless for
compilation, this is the only thing I need to do, i.e. no need to have
another separate branch to send it further on, right?

johannes


  reply	other threads:[~2023-12-11 11:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 11:02 [GIT PULL] mmutable branch between pdx86 amd wbrf branch and wifi / amdgpu due for the v6.8 merge window Hans de Goede
2023-12-11 11:41 ` Johannes Berg [this message]
2023-12-11 11:45   ` Hans de Goede
2023-12-11 14:47 ` Christian König
2023-12-11 15:03   ` Mario Limonciello
2023-12-11 15:27     ` Alex Deucher
2023-12-11 21:46       ` Mario Limonciello
2023-12-12  9:46 ` Johannes Berg
2023-12-12 16:12   ` Mario Limonciello
2023-12-12 16:41     ` Alex Deucher
2023-12-14 16:36 ` Kalle Valo
2023-12-14 16:47   ` Mario Limonciello
2023-12-15  6:35     ` Kalle Valo

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=5e14be1fc61d9d7027cd50f4148eea52e40fb9d3.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Jun.Ma2@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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: 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