kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Anthony Jagers <noonetinone@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Fwd: Later Kernel versions break some games in wine
Date: Sun, 27 Jan 2019 09:29:20 +0100	[thread overview]
Message-ID: <20190127082920.GA4561@kroah.com> (raw)
In-Reply-To: <CANKW2PSs8n8pTw8fmO2QrgjGO5Rmes7NW4d2D_MUncoeCheS7w@mail.gmail.com>

On Fri, Jan 25, 2019 at 11:38:51AM -0500, Anthony Jagers wrote:
> ---------- Forwarded message ---------
> From: Anthony Jagers <noonetinone@gmail.com>
> Date: Fri, Jan 25, 2019 at 11:35 AM
> Subject: Later Kernel versions break some games in wine
> To: <majordomo@vger.kernel.org>

That ^, is not a valid mailing list address.

> Changes in PTRACE_POKEUSER hw breakpoint have broken several games that are
> being ran through wine.
> I must point out that I did not do the bisect, the OP in the wine bug
> report below did that.
> I brought this here because of the dislike among developers in breaking
> user space.  I don't
> know how to proceed from here. Either, wine should adopt code changes or
> the commit below should
> be reverted.
> 
> 
> commit bd14406b78e6daa1ea3c1673bda1ffc9efdeead0
> Author: Jiri Olsa <jolsa@kernel.org>

Please contact all of the developers who contributed to this patch, and
the proper mailing list (you can get that by running the patch through
scripts/get_maintainer.pl) about this, and they will be glad to work on
resolving the issue.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2019-01-27  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANKW2PR-aN=2GhkK0kLjuFiPoceffGS-E5euBFkytV2bK5h3zg@mail.gmail.com>
2019-01-25 16:38 ` Fwd: Later Kernel versions break some games in wine Anthony Jagers
2019-01-27  8:29   ` Greg KH [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=20190127082920.GA4561@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=noonetinone@gmail.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).