From: Kukjin Kim <kgene@kernel.org>
To: 'Wolfram Sang' <wsa@the-dreams.de>,
'Pankaj Dubey' <pankaj.dubey@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, 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: Sat, 22 Nov 2014 09:48:10 +0900 [thread overview]
Message-ID: <019101d005ed$fd3d5eb0$f7b81c10$@kernel.org> (raw)
In-Reply-To: <20141121164726.GA1426@katana>
Wolfram Sang wrote:
>
Hi Wolfram,
> > >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.
Hmm...I think, Pankaj needs to submit separated patches 1) driver change, 2) dt
change and then 3) remove change. And 2nd and 3rd changes should be handed in
Samsung tree together after landing 1) change in -next.
Of course, 1) change should be handled in i2c tree ;)
Thanks,
Kukjin
next prev parent reply other threads:[~2014-11-22 0:48 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
2014-11-22 0:48 ` Kukjin Kim [this message]
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='019101d005ed$fd3d5eb0$f7b81c10$@kernel.org' \
--to=kgene@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=wsa@the-dreams.de \
/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).