From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Kitt <steve@sk2.org>
Cc: Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Russell King <linux@armlinux.org.uk>,
Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/arm: use simple i2c probe function
Date: Sun, 9 Aug 2020 10:38:58 +0200 [thread overview]
Message-ID: <20200809083858.GA7517@kozik-lap> (raw)
In-Reply-To: <20200807153100.384845-1-steve@sk2.org>
On Fri, Aug 07, 2020 at 05:31:00PM +0200, Stephen Kitt wrote:
> The i2c probe functions here don't use the id information provided in
> their second argument, so the single-parameter i2c probe function
> ("probe_new") can be used instead.
>
> This avoids scanning the identifier tables during probes.
>
> Signed-off-by: Stephen Kitt <steve@sk2.org>
> ---
> arch/arm/mach-davinci/board-dm644x-evm.c | 5 ++---
> arch/arm/mach-davinci/board-dm646x-evm.c | 10 ++++------
> arch/arm/mach-s3c64xx/mach-crag6410-module.c | 5 ++---
> 3 files changed, 8 insertions(+), 12 deletions(-)
>
Hi,
You need to split it per sub architecture maintainers. The subject
prefix is then for example: "ARM: s3c64xx: ".
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stephen Kitt <steve@sk2.org>
Cc: Sekhar Nori <nsekhar@ti.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Kukjin Kim <kgene@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arch/arm: use simple i2c probe function
Date: Sun, 9 Aug 2020 10:38:58 +0200 [thread overview]
Message-ID: <20200809083858.GA7517@kozik-lap> (raw)
In-Reply-To: <20200807153100.384845-1-steve@sk2.org>
On Fri, Aug 07, 2020 at 05:31:00PM +0200, Stephen Kitt wrote:
> The i2c probe functions here don't use the id information provided in
> their second argument, so the single-parameter i2c probe function
> ("probe_new") can be used instead.
>
> This avoids scanning the identifier tables during probes.
>
> Signed-off-by: Stephen Kitt <steve@sk2.org>
> ---
> arch/arm/mach-davinci/board-dm644x-evm.c | 5 ++---
> arch/arm/mach-davinci/board-dm646x-evm.c | 10 ++++------
> arch/arm/mach-s3c64xx/mach-crag6410-module.c | 5 ++---
> 3 files changed, 8 insertions(+), 12 deletions(-)
>
Hi,
You need to split it per sub architecture maintainers. The subject
prefix is then for example: "ARM: s3c64xx: ".
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-09 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 15:31 [PATCH] arch/arm: use simple i2c probe function Stephen Kitt
2020-08-07 15:31 ` Stephen Kitt
2020-08-09 8:38 ` Krzysztof Kozlowski [this message]
2020-08-09 8:38 ` Krzysztof Kozlowski
2020-08-09 17:18 ` Stephen Kitt
2020-08-09 17:18 ` Stephen Kitt
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=20200809083858.GA7517@kozik-lap \
--to=krzk@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=steve@sk2.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.