From: Matthias Kaehlcke <mka@chromium.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] frv: Use OFFSET macro in DEF_*REG()
Date: Mon, 17 Apr 2017 13:35:18 -0700 [thread overview]
Message-ID: <20170417203518.GP28657@google.com> (raw)
In-Reply-To: <20170403194636.96438-1-mka@chromium.org>
El Mon, Apr 03, 2017 at 12:46:36PM -0700 Matthias Kaehlcke ha dit:
> Avoid code duplication by using OFFSET() in DEF_*REG() instead of
> replicating the macro.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Ping, any feedback on this patch?
Thanks
Matthias
next prev parent reply other threads:[~2017-04-17 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 19:46 [PATCH] frv: Use OFFSET macro in DEF_*REG() Matthias Kaehlcke
2017-04-17 20:35 ` Matthias Kaehlcke [this message]
2017-04-18 8:26 ` Masahiro Yamada
2017-04-18 9:59 ` David Howells
2017-04-18 10:14 ` Masahiro Yamada
2017-04-23 6:54 ` Masahiro Yamada
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=20170417203518.GP28657@google.com \
--to=mka@chromium.org \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).