From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>,
Jelle van der Waa <jvanderwaa@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
ikepanhc@gmail.com, Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Armin Wolf <W_Armin@gmx.de>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] platform/x86: Move Lenovo files into lenovo subdir
Date: Wed, 11 Jun 2025 18:01:36 +0300 (EEST) [thread overview]
Message-ID: <b8af4da0-bd7f-1d65-8645-73dbd08ff3a8@linux.intel.com> (raw)
In-Reply-To: <002d39fe-44ed-45a4-9410-4fecf1c2163f@app.fastmail.com>
On Tue, 10 Jun 2025, Mark Pearson wrote:
> On Tue, Jun 10, 2025, at 4:27 PM, Andy Shevchenko wrote:
> > On Tue, Jun 10, 2025 at 03:28:25PM -0400, Mark Pearson wrote:
> >> Create lenovo subdirectory for holding Lenovo specific drivers.
> >
> > Assuming Kconfig entries have mostly been copied'n'pasted, the rest LGTM,
>
> Yes - no changes from what they were previously.
Indeed, no changes, too bad that the addition "depends on DMI" was missed
because of that ;-). I've fixed this for you to not delay this patch
further.
A diff-of-pre/post magic trick helps to validate while preparing and
review move changes like this:
diff -u <(grep '^[-]' patch.patch | cut -b 2- | sort) <(grep '^[+]' patch.patch | cut -b 2- | sort)
The sorting is not always needed if no core reordering is done in the
patch but regardless of sorting or not, the unexpected differences are
usually pretty easy to spot from the output of that command. It's how I
found out the lack of depends on DMI on the post side and have found
plenty of similar issue when changes are rebased/reordered in a series
that does contain a move change.
While applying this, I realized I'd taken Jelle's ideapad patch which
resulted in this move patch not applying cleanly, so I ended up moving
Jelle's patch after this change to make things easier for me.
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> Thanks for the reviews and help with both patches
Thanks for doing this, hopefully LKP will be okay with this change too
and we can once again focus on less conflict prone work. :-)
--
i.
next prev parent reply other threads:[~2025-06-11 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 19:28 [PATCH v4 1/2] platform/x86: thinklmi: improved DMI handling Mark Pearson
2025-06-10 19:28 ` [PATCH v4 2/2] platform/x86: Move Lenovo files into lenovo subdir Mark Pearson
2025-06-10 20:27 ` Andy Shevchenko
2025-06-10 23:11 ` Mark Pearson
2025-06-11 15:01 ` Ilpo Järvinen [this message]
2025-06-11 15:07 ` Andy Shevchenko
2025-06-11 15:47 ` Mark Pearson
2025-06-10 20:22 ` [PATCH v4 1/2] platform/x86: thinklmi: improved DMI handling Andy Shevchenko
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=b8af4da0-bd7f-1d65-8645-73dbd08ff3a8@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ikepanhc@gmail.com \
--cc=jvanderwaa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--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 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.