From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Nikita Travkin <nikita@trvn.ru>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [GIT PULL RESEND] Immutable branch between pdx86 lenovo c630 branch, power/supply and USB
Date: Thu, 27 Jun 2024 16:22:32 +0200 [thread overview]
Message-ID: <2024062722-sadness-tiger-a040@gregkh> (raw)
In-Reply-To: <948b6f71-7a72-d03d-c36f-ff4f08987f0d@linux.intel.com>
On Mon, Jun 24, 2024 at 07:44:26PM +0300, Ilpo Järvinen wrote:
> On Mon, 24 Jun 2024, Greg Kroah-Hartman wrote:
>
> > On Mon, Jun 24, 2024 at 07:24:55PM +0300, Ilpo Järvinen wrote:
> > > Hi,
> > >
> > > This is v2 of the lenovo c630 IB branch with the build fix for non-ARM64
> > > platforms (built on top of the commits in the previous IB PR). Resent with
> > > full Subject line.
> > >
> > > The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
> > >
> > > Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git tags/platform-drivers-x86-ib-lenovo-c630-v6.11-2
> > >
> > > for you to fetch changes up to 13bbe1c83bc401c2538c758228d27b4042b08341:
> > >
> > > platform/arm64: build drivers even on non-ARM64 platforms (2024-06-24 18:22:15 +0300)
> >
> > So was the first one rewritten? Or is this just the second patch on
> > top of the previous one?
>
> Nothing was rewritten, just one patch added on top of the previous PR. The
> previous PR had only 2 of these 3 commits:
Now pulled into my tree too, thanks.
greg k-h
prev parent reply other threads:[~2024-06-27 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:24 [GIT PULL RESEND] Immutable branch between pdx86 lenovo c630 branch, power/supply and USB Ilpo Järvinen
2024-06-24 16:28 ` Greg Kroah-Hartman
2024-06-24 16:44 ` Ilpo Järvinen
2024-06-27 14:22 ` Greg Kroah-Hartman [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=2024062722-sadness-tiger-a040@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).