From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
linux-next list <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the driver-core tree
Date: Thu, 8 Oct 2015 12:39:54 +0530 [thread overview]
Message-ID: <20151008070954.GE4570@linux> (raw)
In-Reply-To: <1846544.jnahGernn9@vostro.rjw.lan>
On 08-10-15, 00:47, Rafael J. Wysocki wrote:
> Well, the conflicting commits here were from the same developer which is kind
> of annoying.
I do understand why its annoying, but I wasn't doing them in parallel.
The patches in Greg's tree were written long after the other series
got applied to your tree.
So, I was kind of helpless here :(
> The new use in my tree can wait until the API update in the Greg's tree is
> merged IMO. That's why I've now dropped the commit that added it. :-)
Looking at the current state of your tree, looks like you have dropped
way too many patches. Was it intentional?
Missing commits:
1840995c52d4 PM / OPP: reuse of_parse_phandle()
f0489a5ef4d0 PM / OPP: Rename opp init/free table routines
8f8d37b2537a PM / OPP: Prefix exported opp routines with dev_pm_opp_
33692dc381f9 PM / OPP: Move opp core to its own directory
f59d3ee8480d PM / OPP: Move cpu specific code to opp/cpu.c
5cb5fdbf3877 PM / OPP: Add debugfs support
I though you just dropped the last commit, but no.
--
viresh
next prev parent reply other threads:[~2015-10-08 7:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 4:51 linux-next: build warning after merge of the driver-core tree Stephen Rothwell
2015-10-07 6:40 ` Viresh Kumar
2015-10-07 21:48 ` Rafael J. Wysocki
2015-10-07 22:04 ` Stephen Rothwell
2015-10-07 22:47 ` Rafael J. Wysocki
2015-10-08 7:09 ` Viresh Kumar [this message]
2015-10-08 20:30 ` Rafael J. Wysocki
2015-10-09 5:36 ` Stephen Rothwell
2015-10-09 6:31 ` Viresh Kumar
2015-10-09 20:49 ` Rafael J. Wysocki
2015-10-09 6:37 ` Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 11:35 Stephen Rothwell
2023-03-27 1:03 Stephen Rothwell
2023-03-27 7:31 ` Greg KH
2023-02-20 5:31 Stephen Rothwell
2023-02-20 7:26 ` Qi Zheng
2023-02-20 7:31 ` Greg KH
2023-02-20 9:49 ` Bagas Sanjaya
2023-02-20 10:15 ` Qi Zheng
2023-02-20 10:50 ` Greg KH
2023-02-20 11:01 ` Qi Zheng
2022-05-01 22:36 Stephen Rothwell
2021-12-06 8:30 Stephen Rothwell
2021-12-06 12:53 ` Heiko Carstens
2021-12-07 10:23 ` Greg KH
2020-09-09 7:23 Stephen Rothwell
2020-09-09 7:40 ` Greg KH
2019-08-05 3:04 Stephen Rothwell
2019-08-05 4:56 ` Stephen Rothwell
2019-08-06 0:03 ` Saravana Kannan
2019-08-01 5:05 Stephen Rothwell
2019-08-01 6:10 ` Greg KH
2019-07-04 6:24 Stephen Rothwell
2019-07-04 8:21 ` Greg KH
2019-07-04 6:17 Stephen Rothwell
2019-07-04 6:30 ` Greg KH
2013-06-25 8:33 Stephen Rothwell
2013-06-25 12:00 ` Ming Lei
2011-02-21 6:02 Stephen Rothwell
2011-02-21 6:32 ` Greg KH
2011-02-21 20:18 ` Ilya Yanok
2011-02-21 5:37 Stephen Rothwell
2011-02-21 5:50 ` Stephen Rothwell
2011-02-21 6:31 ` Greg KH
2011-03-17 23:10 ` Stephen Rothwell
2010-09-02 3:18 Stephen Rothwell
2010-09-02 3:29 ` Greg KH
2010-09-02 10:14 ` Thomas Renninger
2010-09-02 19:59 ` Greg KH
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=20151008070954.GE4570@linux \
--to=viresh.kumar@linaro.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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).