linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Set PLT entry/header sizes properly on Sparc.
Date: Thu, 18 Oct 2018 11:22:29 -0300	[thread overview]
Message-ID: <20181018142229.GD3254@redhat.com> (raw)
In-Reply-To: <20181017.120859.2268840244308635255.davem@davemloft.net>

Em Wed, Oct 17, 2018 at 12:08:59PM -0700, David Miller escreveu:
> 
> Using the sh_entsize for both values isn't correct.  It happens
> to be correct on x86...
> 
> For both 32-bit and 64-bit sparc, there are four PLT entries in the
> PLT section.

Thanks, applied.

- Arnaldo

  reply	other threads:[~2018-10-18 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 19:08 [PATCH] perf: Set PLT entry/header sizes properly on Sparc David Miller
2018-10-18 14:22 ` Arnaldo Carvalho de Melo [this message]
2018-10-26  7:29 ` [tip:perf/urgent] perf symbols: " tip-bot for David Miller

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=20181018142229.GD3254@redhat.com \
    --to=acme@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.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 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).