From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: sedat.dilek@gmail.com
Cc: Andre Przywara <andre.przywara@amd.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg@redhat.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Thomas Renninger <trenn@suse.de>
Subject: Re: linux-next: Tree for Sept 6 (does not boot on AMD64)
Date: Thu, 6 Sep 2012 23:24:15 +0200 [thread overview]
Message-ID: <201209062324.15297.rjw@sisk.pl> (raw)
In-Reply-To: <CA+icZUW_wkFA5giQGWeVypMtD3coT8FBwzZ6bNSEOvfasCAF_g@mail.gmail.com>
On Thursday, September 06, 2012, Sedat Dilek wrote:
> On Thu, Sep 6, 2012 at 11:17 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Thursday, September 06, 2012, Sedat Dilek wrote:
[...]
> >>
> >> Just wondering... Fell over it when digging into my boot-problem (this
> >> appeared as a new Kconfig option, so).
> >> Thanks for the explanations!
> >
> > Ah, OK. I got the impression that the patchset caused a problem to happen for
> > you. I suppose it's fine to keep it in linux-next after all, then?
> >
>
> Please, keep it!
> My system boots with the slab-next-fixes!
> My apologies for my curiosity - asking should be allowed, anyway :-).
Sure, no problem with that. Thanks for the clarification.
Rafael
prev parent reply other threads:[~2012-09-06 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 11:48 linux-next: Tree for Sept 6 (does not boot on AMD64) Sedat Dilek
2012-09-06 13:35 ` Sedat Dilek
2012-09-06 20:08 ` Rafael J. Wysocki
2012-09-06 20:30 ` Sedat Dilek
2012-09-06 20:50 ` Andre Przywara
2012-09-06 20:53 ` Sedat Dilek
2012-09-06 21:17 ` Rafael J. Wysocki
2012-09-06 21:15 ` Sedat Dilek
2012-09-06 21:24 ` 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=201209062324.15297.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=andre.przywara@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=trenn@suse.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).