From: Wolfram Sang <wsa@kernel.org>
To: Adam Borowski <kilobyte@angband.pl>,
Khalil Blaiech <kblaiech@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] i2c: mlxbf: depend on ACPI; clean away ifdeffage
Date: Fri, 21 Oct 2022 08:47:46 +0200 [thread overview]
Message-ID: <Y1JAkptx2esnE5BB@shikoro> (raw)
In-Reply-To: <Y1I/hRG9XGTFDTr3@shikoro>
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
> > Fixes: be18c5ede25da39a0eda541f6de3620a30cf731f
BTW this has to look like:
Fixes: be18c5ede25d ("i2c: mlxbf: remove device tree support")
checkpatch will warn you about it. This time, I fixed it for you.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-21 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S229853AbiJTWkg/20221020224036Z+12888@vger.kernel.org>
2022-10-10 18:33 ` [PATCH 5/6] i2c: mlxbf: depend on ACPI; clean away ifdeffage Adam Borowski
2022-10-21 6:43 ` Wolfram Sang
2022-10-21 6:47 ` Wolfram Sang [this message]
2022-10-21 12:43 ` Asmaa Mnebhi
2022-10-21 12:57 ` Khalil Blaiech
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=Y1JAkptx2esnE5BB@shikoro \
--to=wsa@kernel.org \
--cc=asmaa@nvidia.com \
--cc=kblaiech@nvidia.com \
--cc=kilobyte@angband.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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