From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: Re: [GIT PULL] Some error injection fixes to queue for 3.11
Date: Thu, 20 Jun 2013 01:17 +0200 [thread overview]
Message-ID: <1565630.1FKRuXAmOU@vostro.rjw.lan> (raw)
In-Reply-To: <1A7043D5F58CCB44A599DFD55ED4C94838515269@FMSMSX106.amr.corp.intel.com>
On Wednesday, June 19, 2013 05:01:52 PM Brown, Len wrote:
> > >> Pulled, thanks Tony!
> > >>
> > >> Len, are you fine with this route [tip:x86/ras tree] for the
> > >> drivers/acpi/apei/einj.c changes?
> > >
> > > Yes, the RAS guys basically own that code.
> >
> > These patches also got picked up by Rafael and are in his ACPI tree
> > too. I think the patches were applied identically, so there should not
> > be any merge conflicts when this all comes back together in the 3.11
> > merge window.
> >
> > Rafael already had a chat about who will take future apei changes
> > so that we won't have this happen again.
>
> I think the only real problem with being in two places at once
> is if the patches _change_. When that happens, you need to
> get them _both_ changed, else merge conflict happens at the worst time.
I dropped the APEI patches from my tree.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-06-19 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 16:10 Luck, Tony
2013-06-19 11:57 ` Ingo Molnar
2013-06-19 15:29 ` Brown, Len
2013-06-19 16:40 ` Luck, Tony
2013-06-19 17:01 ` Brown, Len
2013-06-19 23:17 ` 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=1565630.1FKRuXAmOU@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bp@alien8.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®