linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
	<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>
Cc: <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 13/20] arc: migrate exception table users off module.h and onto extable.h
Date: Mon, 23 Jan 2017 13:14:04 -0800	[thread overview]
Message-ID: <b8c3cef5-ad62-1e2f-499c-b80816a88469@synopsys.com> (raw)
In-Reply-To: <20170122163244.11740-14-paul.gortmaker@windriver.com>

On 01/22/2017 08:32 AM, Paul Gortmaker wrote:
> This file was only including module.h for exception table related
> functions.  We've now separated that content out into its own file
> "extable.h" so now move over to that and avoid all the extra header
> content in module.h that we don't really need to compile this file.
> Since the file does have some EXPORT_SYMBOL, we add export.h include.
> 
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: linux-snps-arc@lists.infradead.org
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

Acked-by: Vineet Gupta <vgupta@synopsys.com>

Thx,
-Vineet

  reply	other threads:[~2017-01-23 21:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 16:32 [PATCH v3 00/20] Finalize separation of extable.h from module.h Paul Gortmaker
2017-01-22 16:32 ` [PATCH 01/20] ia64: move ia64_done_with_exception out of asm/uaccess.h Paul Gortmaker
2017-01-22 16:32 ` [PATCH 02/20] ia64: ensure exception table search users include extable.h Paul Gortmaker
2017-01-22 16:32 ` [PATCH 03/20] m32r: migrate exception table users off module.h and onto extable.h Paul Gortmaker
2017-01-22 16:32 ` [PATCH 04/20] arm: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 05/20] alpha: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 06/20] mn10300: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 07/20] xtensa: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 08/20] sh: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 09/20] frv: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 10/20] openrisc: " Paul Gortmaker
2017-01-25 21:40   ` [PATCH v2] " Paul Gortmaker
2017-01-26  5:53     ` Stafford Horne
2017-01-26 14:50       ` Paul Gortmaker
2017-01-25 22:46   ` Paul Gortmaker
2017-01-22 16:32 ` [PATCH 11/20] sparc: migrate exception table users " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 12/20] nios2: migrate exception table users off module.h and " Paul Gortmaker
2017-01-25  9:53   ` Tobias Klauser
2017-01-22 16:32 ` [PATCH 13/20] arc: " Paul Gortmaker
2017-01-23 21:14   ` Vineet Gupta [this message]
2017-01-22 16:32 ` [PATCH 14/20] metag: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 15/20] score: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 16/20] unicore32: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 17/20] microblaze: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 18/20] hexagon: " Paul Gortmaker
2017-01-22 16:32 ` [PATCH 19/20] core: " Paul Gortmaker
2017-02-09  5:33   ` Jessica Yu
2017-01-22 16:32 ` [PATCH 20/20] module.h: remove extable.h include now users have migrated Paul Gortmaker
2017-01-22 22:52   ` kbuild test robot
2017-01-23  4:16     ` Paul Gortmaker
2017-02-09  5:34   ` Jessica Yu

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=b8c3cef5-ad62-1e2f-499c-b80816a88469@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=paul.gortmaker@windriver.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).