regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Christoph Hellwig" <hch@lst.de>,
	"kernel test robot" <oliver.sang@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Serge Belyshev" <belyshev@depni.sinp.msu.ru>,
	"Chris Wilson" <chris@chris-wilson.co.uk>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, "kernel test robot" <lkp@intel.com>,
	regressions@lists.linux.dev
Subject: Re: [i915] b12d691ea5: kernel_BUG_at_mm/memory.c
Date: Wed, 19 May 2021 06:31:31 -1000	[thread overview]
Message-ID: <CAHk-=wgEZrsY9tsyC=+2sXVVuBDiZDTSMxt-X5LgwvSQqs_a6w@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgYqF3bffW0EPmVTUFcoV0jXECu-A_dyWZ0ZwUwhCHi+A@mail.gmail.com>

On Wed, May 19, 2021 at 6:11 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, May 19, 2021 at 5:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > Christoph Hellwig <hch@lst.de> writes:
> >
> > > On Tue, May 18, 2021 at 04:58:31PM -1000, Linus Torvalds wrote:
> > >>
> > >> I'd be inclined to revert the commits as "not ready yet", but it would
> > >> be better if somebody can go "yeah, this should be done properly like
> > >> X".
> > >
> > > I think reverting just this commit for now is the best thing.
> >
> > Yes, please revert it if there's no quick fix. On my Dell XPS 13 9310
> > laptop (with Debian 10) X won't start until I revert commit
> > b12d691ea5e0, so this is a major issue.
>
> Reverted.

Oh, and Christoph - there were a couple of preparatory patches before
that one. They all looked syntactic to me, but it might be best to
check that reverting just this one commit is ok?

                   Linus

      reply	other threads:[~2021-05-19 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210519024322.GA29704@xsang-OptiPlex-9020>
     [not found] ` <CAHk-=whcr5M=4Mz2ydu4XtxTL_34WkXPnmFmA4f8r+ELXDC6hg@mail.gmail.com>
     [not found]   ` <20210519133330.GA14452@lst.de>
2021-05-19 15:00     ` [i915] b12d691ea5: kernel_BUG_at_mm/memory.c Kalle Valo
2021-05-19 16:11       ` Linus Torvalds
2021-05-19 16:31         ` Linus Torvalds [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='CAHk-=wgEZrsY9tsyC=+2sXVVuBDiZDTSMxt-X5LgwvSQqs_a6w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=hch@lst.de \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=regressions@lists.linux.dev \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.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;
as well as URLs for NNTP newsgroup(s).