From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Chen-Yu Tsai <wenst@chromium.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] i2c: Use *-y instead of *-objs in Makefile
Date: Mon, 4 Nov 2024 13:20:32 +0200 [thread overview]
Message-ID: <ZyiuAIgubo4oZ5dw@smile.fi.intel.com> (raw)
In-Reply-To: <ZyiqcHFJFFnBYmTN@shikoro>
On Mon, Nov 04, 2024 at 01:05:20PM +0200, Wolfram Sang wrote:
>
> > > Shouldn't be separated commit anyway?
>
> Can be argued.
I have an evidence for my side: LKP complained as my (thanks to be a separate)
patch unveiled the issue in the Kconfig there. Meaning that required a new version
of the change, while the core part is not affected anyhow.
> This patch applied to for-next, thanks!
Thank you!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-11-04 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:03 [PATCH v1 1/1] i2c: Use *-y instead of *-objs in Makefile Andy Shevchenko
2024-11-01 12:24 ` Andy Shevchenko
2024-11-01 12:43 ` Wolfram Sang
2024-11-01 13:06 ` Andy Shevchenko
2024-11-01 13:12 ` Andy Shevchenko
2024-11-04 11:05 ` Wolfram Sang
2024-11-04 11:20 ` Andy Shevchenko [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=ZyiuAIgubo4oZ5dw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wenst@chromium.org \
--cc=wsa+renesas@sang-engineering.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