All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [GIT pull] perf fixes for 5.6-rc1
Date: Sun, 9 Feb 2020 12:06:47 -0800	[thread overview]
Message-ID: <CAHk-=wiEg6+j1UuRSAZmXozJEw0p33gM9uPT2oAOFwsOUaa=uw@mail.gmail.com> (raw)
In-Reply-To: <158125695732.26104.3631526665331853849.tglx@nanos.tec.linutronix.de>

On Sun, Feb 9, 2020 at 6:06 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
>    - Prevent am intgeer underflow in the perf mlock acounting
>
>    - Add a missing prototyp for arch_perf_update_userpage()
>
>    - Fix the perf parser so it does not delete parse event terms, which
>      caused a regression for using perf with the ARM CoreSight as the sink
>      confuguration was missing due to the deletion.

You've started drinking too early in the day.  But hey, I guess it was
evening _somewhere_ in the world.

Pick out the five speeling errors in that pull request message.

               Linus

  reply	other threads:[~2020-02-09 20:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 14:02 [GIT pull] EFI fix for 5.6-rc1 Thomas Gleixner
2020-02-09 14:02 ` [GIT pull] interrupt fixes " Thomas Gleixner
2020-02-09 20:40   ` pr-tracker-bot
2020-02-09 14:02 ` [GIT pull] perf " Thomas Gleixner
2020-02-09 20:06   ` Linus Torvalds [this message]
2020-02-09 20:53     ` Thomas Gleixner
2020-02-09 21:07       ` Linus Torvalds
2020-02-09 22:21     ` Randy Dunlap
2020-02-09 20:40   ` pr-tracker-bot
2020-02-09 14:02 ` [GIT pull] time(r) " Thomas Gleixner
2020-02-09 20:40   ` pr-tracker-bot
2020-02-09 14:02 ` [GIT pull] x86 " Thomas Gleixner
2020-02-09 20:40   ` pr-tracker-bot
2020-02-09 14:02 ` [GIT pull] SMP " Thomas Gleixner
2020-02-09 20:40   ` pr-tracker-bot
2020-02-09 20:40 ` [GIT pull] EFI fix " pr-tracker-bot

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-=wiEg6+j1UuRSAZmXozJEw0p33gM9uPT2oAOFwsOUaa=uw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.