All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Stefan Dirsch <sndirsch@suse.com>,
	Thomas Zimmermann <tzimmermann@suse.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 4f5368b5541a902f6596558b05f5c21a9770dd32 causes regression
Date: Mon, 30 Sep 2019 14:46:43 +0200	[thread overview]
Message-ID: <1569847603.2639.0.camel@suse.com> (raw)
In-Reply-To: <CAKMK7uHicakgeTEUhK63R4yKh+HMHCmy11L_o5PCSJoLG65BYg@mail.gmail.com>

Am Mittwoch, den 25.09.2019, 21:48 +0200 schrieb Daniel Vetter:
> which undoes any side-effect of the patch you're pointing at. I am
> rather surprised though that this results in a hard-lookup for you,
> did you confirm the bisect by reverting that commit on top of latest
> upstream?

Hi,

yes, a straight revert fixes the issue.

	Regards
		Oliver


      reply	other threads:[~2019-09-30 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 19:22 4f5368b5541a902f6596558b05f5c21a9770dd32 causes regression Oliver Neukum
2019-09-25 19:47 ` Al Viro
2019-09-25 19:48 ` Daniel Vetter
2019-09-30 12:46   ` Oliver Neukum [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=1569847603.2639.0.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sndirsch@suse.com \
    --cc=tzimmermann@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.