linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: linux-next: manual merge of the pm tree with the pci tree
Date: Wed, 11 Feb 2015 02:41:35 +0100	[thread overview]
Message-ID: <1544592.4ITKEDgnAg@vostro.rjw.lan> (raw)
In-Reply-To: <20150211120755.50217078@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Wednesday, February 11, 2015 12:07:55 PM Stephen Rothwell wrote:
> Hi Rafael,
> 
> Today's linux-next merge of the pm tree got a conflict in
> drivers/of/of_pci.c between commit d2be00c0fb5a ("of/pci: Free
> resources on failure in of_pci_get_host_bridge_resources()") from the
> pci tree and commit 5c493df25a0d ("Merge branch 'pci/host-generic' of
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci into
> acpi-resources") from the pm tree.
> 
> I fixed it up (I just use the latter version, please check when it
> comes out) and can carry the fix as necessary (no action is required,
> though someone might want to tell Linus how to resolve it - including
> the removal of the "kfree(bus_range);").

Sorry, I messed this up.  The commit that supposed to be a merge ended
up as a non-merge commit in my tree, just because I tried to modify
the changelog of it without doing the merge again.

Then, I should have noticed that when I was putting together the pull request
for Linus earlier today, but then I didn't.

Rafael

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-02-11  1:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  1:07 linux-next: manual merge of the pm tree with the pci tree Stephen Rothwell
2015-02-11  1:41 ` Rafael J. Wysocki [this message]
2015-02-11  2:03   ` Rafael J. Wysocki
2015-02-11  2:05     ` Lorenzo Pieralisi
  -- strict thread matches above, loose matches on Subject: below --
2019-11-24 23:13 Stephen Rothwell
2019-11-25 14:06 ` Rafael J. Wysocki
2019-11-27 23:58 ` Stephen Rothwell
2019-07-01  3:24 Stephen Rothwell
2013-06-27  3:02 Stephen Rothwell
2013-04-16  2:46 Stephen Rothwell
2013-04-16 17:53 ` Rafael J. Wysocki
2013-02-20  1:55 Stephen Rothwell
2013-02-20 12:57 ` Rafael J. Wysocki
2013-02-18  1:17 Stephen Rothwell
2013-02-18 12:28 ` Rafael J. Wysocki
2013-02-18  1:11 Stephen Rothwell
2013-02-18 12:30 ` Rafael J. Wysocki
2013-02-15  1:23 Stephen Rothwell
2013-02-15 12:51 ` Rafael J. Wysocki
2013-01-30  8:35 Stephen Rothwell
2013-01-30 12:48 ` Rafael J. Wysocki
2013-01-10  0:28 Stephen Rothwell
2013-01-10 13:12 ` Rafael J. Wysocki
2013-01-10 18:30   ` Bjorn Helgaas
2012-11-06  2:48 Stephen Rothwell
2012-11-06 16:52 ` Bjorn Helgaas
2012-11-16 10:17   ` Rafael J. Wysocki

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=1544592.4ITKEDgnAg@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --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).