From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Zheng, Lv" <lv.zheng@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chen, Gong" <gong.chen@linux.intel.com>
Subject: Re: linux-next: manual merge of the pm tree with the ia64 tree
Date: Wed, 16 Jul 2014 23:53:26 +0200 [thread overview]
Message-ID: <1945215.v4beMAkkaN@vostro.rjw.lan> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E8802641B27@SHSMSX101.ccr.corp.intel.com>
On Wednesday, July 16, 2014 03:06:13 AM Zheng, Lv wrote:
> Hi,
>
> > From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
> > Sent: Tuesday, July 15, 2014 8:15 PM
> >
> > On Tuesday, July 15, 2014 01:56:20 PM Stephen Rothwell wrote:
> > >
> > > --Sig_/Cs291xJCrI1kc_+PiCdNT0M
> > > Content-Type: text/plain; charset=US-ASCII
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > Hi Rafael,
> > >
> > > Today's linux-next merge of the pm tree got a conflict in
> > > drivers/acpi/acpi_extlog.c between commits 2dfb7d51a61d ("trace, RAS:
> > > Add eMCA trace event interface") and d6cae935ec5b ("trace, eMCA: Add a
> > > knob to adjust where to save event log") from the ia64 tree and commit
> > > 0a00fd5e20fd ("ACPICA: Restore error table definitions to reduce code
> > > differences between Linux and ACPICA upstream") from the pm tree.
> > >
> > > I fixed it up (hopefully - see below) and can carry the fix as
> > > necessary (no action is required).
> >
> > Thanks for fixing this up!
> >
> > Lv, can you please check if acpi_extlog.c is fine in linux-next?
>
> I checked.
>
> There is no problem in rafael/linux-pm.git/linux-next branch.
> The 2 commits:
> trace, RAS: Add eMCA trace event interface
> trace, eMCA: Add a knob to adjust where to save event log
> are not in torvalds/linux.git/master branch, I found them in aegl/linux.git/next branch.
>
> So if torvalds/linux.git/master merges rafael/linux-pm.git/linux-next before merging aegl/linux.git/next, we will need the following fix.
> And the following collision fix is correct.
Thanks for checking!
Rafael
prev parent reply other threads:[~2014-07-16 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 3:56 linux-next: manual merge of the pm tree with the ia64 tree Stephen Rothwell
2014-07-15 12:15 ` Rafael J. Wysocki
2014-07-16 3:06 ` Zheng, Lv
2014-07-16 21:53 ` Rafael J. Wysocki [this message]
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=1945215.v4beMAkkaN@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.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