From: Wolfram Sang <wsa@the-dreams.de>
To: Pankaj Dubey <pankaj.dubey@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
linux@arm.linux.org.uk, thomas.ab@samsung.com,
Rob Herring <robh+dt@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 1/2] i2c: s3c2410: Handle i2c sys_cfg register in i2c driver
Date: Fri, 21 Nov 2014 17:47:26 +0100 [thread overview]
Message-ID: <20141121164726.GA1426@katana> (raw)
In-Reply-To: <546F1140.4050709@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
> >I usually don't take DTS patches. They should go via arm-soc. Please say
> >so if there are reasons I should take them.
>
> I CC'ed to you because same patch contains changes in i2c driver.
Yes, those should absolutely go via my I2C tree. You need to make a
seperate patch out of the dts changes which then also should go via
samsung-soc, unless Kukjin says he really wants to go the via I2C. But I
guess the latter will just create merge conflicts.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-21 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1414656270-8048-1-git-send-email-pankaj.dubey@samsung.com>
2014-10-30 8:04 ` [PATCH v4 1/2] i2c: s3c2410: Handle i2c sys_cfg register in i2c driver Pankaj Dubey
2014-11-21 7:25 ` Wolfram Sang
2014-11-21 10:17 ` Pankaj Dubey
2014-11-21 16:47 ` Wolfram Sang [this message]
2014-11-22 0:48 ` Kukjin Kim
2014-11-24 9:01 ` Pankaj Dubey
2014-11-22 0:42 ` Kukjin Kim
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=20141121164726.GA1426@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pankaj.dubey@samsung.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=thomas.ab@samsung.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;
as well as URLs for NNTP newsgroup(s).