linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: yamada.masahiro@socionext.com (Masahiro Yamada)
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 17:27:22 +0900	[thread overview]
Message-ID: <CAK7LNATVmVi=4ugv0MgoCUzusphNeAXTC_K-PsXDiTLoCkV4-Q@mail.gmail.com> (raw)
In-Reply-To: <20151026081746.GC597@x1>

Hi Lee,


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.





-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2015-10-26  8:27 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 [this message]
2015-10-26  8:31     ` Geert Uytterhoeven
2015-10-26  8:35       ` Wolfram Sang
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='CAK7LNATVmVi=4ugv0MgoCUzusphNeAXTC_K-PsXDiTLoCkV4-Q@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --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;
as well as URLs for NNTP newsgroup(s).