From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Rashmica Gupta <rashmicy@gmail•com>,
benh@kernel•crashing.org, linuxppc-dev@lists•ozlabs.org
Subject: Re: [1/3] powerpc/asm: Use OFFSET macro in asm-offsets.c
Date: Thu, 16 Feb 2017 16:59:45 +1100 (AEDT) [thread overview]
Message-ID: <3vP58d0hh2z9s8X@ozlabs.org> (raw)
In-Reply-To: <1464841788-17465-1-git-send-email-rashmicy@gmail.com>
On Thu, 2016-06-02 at 04:29:46 UTC, Rashmica Gupta wrote:
> A lot of entries in asm-offests.c look like this:
> DEFINE(TI_FLAGS, offsetof(struct thread_info, flags));
>
> But there is a common macro, OFFSET, which makes this cleaner:
> OFFSET(TI_flags, thread_info, flags), so use this.
>
> Signed-off-by: Rashmica Gupta <rashmicy@gmail•com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/454656155110603e88b83eec847d52
cheers
prev parent reply other threads:[~2017-02-16 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 4:29 [PATCH 1/3] powerpc/asm: Use OFFSET macro in asm-offsets.c Rashmica Gupta
2016-06-02 4:29 ` [PATCH 2/3] powerpc/asm: Define STACK_OFFSET " Rashmica Gupta
2017-02-16 5:59 ` [2/3] " Michael Ellerman
2016-06-02 4:29 ` [PATCH 3/3] powerpc/asm: Add STACK_INT_OFFSET " Rashmica Gupta
2017-02-16 5:59 ` Michael Ellerman [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=3vP58d0hh2z9s8X@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=rashmicy@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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