All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: PDx86 ML <platform-driver-x86@vger.kernel.org>,
	 Hans de Goede <hansg@kernel.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Imminent rebase of pdx86 trees to v7.2-rc2
Date: Mon, 6 Jul 2026 11:48:18 +0300 (EEST)	[thread overview]
Message-ID: <8084b592-cb10-2ae4-603a-615f053ca01d@linux.intel.com> (raw)

Hi all,

Because of the recent mid-rc-cycle merge of the rework for 
mod_devicetable.h in d2c9a99135da ("Merge tag 'device-id-rework' of 
git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux"), I'll be 
(re)basing our pdx86 tree on top of v7.2-rc2.

This has already happened for the review-ilpo-next branch where from it 
will propagate to for-next once the build test completes. The propagation 
is expected to take a day or two unless LKP decides to not cooperate or 
there is a build issue.

For the fixes (and review-ilpo-fixes) branch, the new base will be used 
after the next PR has been made.

The potential conflicts will be in #include block only so if your patch is 
touching header includes, please make sure you're based on a fresh commit 
from pdx86 repo before submitting.

I'm sorry for any inconvenience.

-- 
 i.


             reply	other threads:[~2026-07-06  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  8:48 Ilpo Järvinen [this message]
2026-07-06 10:37 ` Imminent rebase of pdx86 trees to v7.2-rc2 Uwe Kleine-König
2026-07-06 15:02   ` Andy Shevchenko
2026-07-07  8:24     ` Uwe Kleine-König
2026-07-07  9:14       ` 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=8084b592-cb10-2ae4-603a-615f053ca01d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hansg@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.