From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform
Date: Mon, 26 Oct 2015 09:35:41 +0100 [thread overview]
Message-ID: <20151026083541.GB3041@katana> (raw)
In-Reply-To: <CAMuHMdXLMRji80Ma9hbUJg_PChS1s2JaGy00L3M3rmyOnYKqHQ@mail.gmail.com>
On Mon, Oct 26, 2015 at 09:31:15AM +0100, Geert Uytterhoeven wrote:
> On Mon, Oct 26, 2015 at 9:27 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
> > 2015-10-26 17:17 GMT+09:00 Lee Jones <lee.jones@linaro.org>:
> >>> This series adds two I2C controller drivers.
> >>> (they are completely different IPs.)
> >>>
> >>> The first one is a very simple FIFO-less I2C controller,
> >>> which is used on some older UniPhier SoCs.
> >>>
> >>> The other one is higher-performance I2C controller with TX/RX FIFO,
> >>> used on newer UniPhier SoCs.
> >>
> >> And you have sent this to me because ... ?
> >
> >
> > No special reason.
> >
> >
> > I sent this series to linux-i2c at vger.kernel.org.
> >
> > I guess you were automatically CC'ed by scripts/get_maintainer.pl.
> >
> > Using get_maintainer.pl is a normal process when sending patches, I think.
>
> Please use common sense. It doesn't make much sense to CC everybody who
> ever made a minor edit to an affected file.
>
> If checkpatch comes up with more than 5 names, this should ring a bell.
I usually use get_maintainer.pl with --no-git-fallback to catch people
listed in MAINTAINERS only. But mileages vary a lot in that area.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151026/ef2be939/attachment.sig>
next prev parent reply other threads:[~2015-10-26 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 10:51 [PATCH v2 0/2] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform Masahiro Yamada
2015-10-23 10:51 ` [PATCH v2 1/2] i2c: uniphier: add UniPhier FIFO-less I2C driver Masahiro Yamada
2015-10-23 11:49 ` Wolfram Sang
2015-10-23 10:52 ` [PATCH v2 2/2] i2c: uniphier_f: add UniPhier FIFO-builtin " Masahiro Yamada
2015-10-23 11:49 ` Wolfram Sang
2015-10-26 8:17 ` [PATCH v2 0/2] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform Lee Jones
2015-10-26 8:27 ` Masahiro Yamada
2015-10-26 8:31 ` Geert Uytterhoeven
2015-10-26 8:35 ` Wolfram Sang [this message]
2015-10-26 10:47 ` Lee Jones
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=20151026083541.GB3041@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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