From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh@kernel.org>
Cc: Sam Povilus <kernel.development@povil.us>,
Wolfram Sang <wsa@the-dreams.de>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH v5] hwmon: ads7828 optional parameters from the device tree
Date: Fri, 24 Mar 2017 12:55:26 -0700 [thread overview]
Message-ID: <20170324195526.GA28270@roeck-us.net> (raw)
In-Reply-To: <20170324161003.hv2bqpyspjdkx5j4@rob-hp-laptop>
On Fri, Mar 24, 2017 at 11:10:03AM -0500, Rob Herring wrote:
> On Wed, Mar 22, 2017 at 07:05:55AM -0600, Sam Povilus wrote:
> > On Wed, Mar 22, 2017 at 09:42:40AM +0100, Wolfram Sang wrote:
> > >
> > > > .../devicetree/bindings/i2c/trivial-devices.txt | 2 --
> > >
> > > This file is about to get moved one directory up:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?h=dt/next&id=b7e252fcddfa573bb1ee275b53bba6cef85671d4
> > >
> > > Just so you know already...
> > >
> >
> > Thanks! I'm a bit new to this, what's the best way for me to handle
> > this? Submit against Linus' tree (presumably making a merge nightmare
> > for someone) or rebase my branch off robh's (and presumably risking some
> > other branch's patch conflicting)?
>
> Send me a separate patch for just this file and I'll pick it up.
>
Agreed, that seems to be the best approach.
Thanks,
Guenter
next prev parent reply other threads:[~2017-03-24 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 3:24 [PATCH v5] hwmon: ads7828 optional parameters from the device tree Sam Povilus
[not found] ` <20170321032434.9268-1-kernel.development-iezDrKAjiWs@public.gmane.org>
2017-03-21 5:59 ` Guenter Roeck
2017-03-22 8:42 ` Wolfram Sang
2017-03-22 13:05 ` Sam Povilus
[not found] ` <20170322130555.wgwrkeju43dvj232-vsA/HdQuLiGu4arkomUJ35yrNiDsoR7y@public.gmane.org>
2017-03-22 21:36 ` Wolfram Sang
2017-03-24 16:10 ` Rob Herring
2017-03-24 19:55 ` Guenter Roeck [this message]
2017-03-24 16:12 ` Rob Herring
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=20170324195526.GA28270@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kernel.development@povil.us \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--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).