From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: mach-omap2: remove bogus "or_module" from rx51-peripherals
Date: Sat, 23 Jul 2016 10:14:22 -0400 [thread overview]
Message-ID: <20160723141421.GC12632@windriver.com> (raw)
In-Reply-To: <20160723055524.GA28140@atomide.com>
[Re: [PATCH 1/3] ARM: mach-omap2: remove bogus "or_module" from rx51-peripherals] On 22/07/2016 (Fri 22:55) Tony Lindgren wrote:
> * Paul Gortmaker <paul.gortmaker@windriver.com> [160722 07:02]:
[...]
> > Having the patch present, or having the file deleted both take care of
> > my concern -- which was was introducing build regressions when adding
> > the gpio header cleanup into for-4.9 content.
>
> OK. As I've already pushed out the board-*.c removal branch, I
> suggest we just drop the $subject patch to avoid a merge conflict.
Sounds like a plan. I'll just keep it in my local queue so my tests
don't fail and drop it on the floor once I see your removal loop around
to me via linux-next or master.
Thanks,
Paul.
--
>
> Regards,
>
> Tony
next prev parent reply other threads:[~2016-07-23 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 4:13 [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio Paul Gortmaker
2016-07-20 4:13 ` [PATCH 1/3] ARM: mach-omap2: remove bogus "or_module" from rx51-peripherals Paul Gortmaker
2016-07-22 6:41 ` Tony Lindgren
2016-07-22 14:02 ` Paul Gortmaker
2016-07-23 5:55 ` Tony Lindgren
2016-07-23 14:14 ` Paul Gortmaker [this message]
2016-07-20 4:13 ` [PATCH 2/3] ARM: pxa: add module.h for corgi symbol_get/symbol_put usage Paul Gortmaker
2016-07-20 4:13 ` [PATCH 3/3] ARM: pxa: add module.h for spitz " Paul Gortmaker
2016-07-22 15:29 ` [PATCH 0/3] ARM: fix three implicit module use cases fed via gpio Linus Walleij
2016-07-23 8:09 ` Robert Jarzmik
2016-07-23 14:10 ` Paul Gortmaker
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=20160723141421.GC12632@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-arm-kernel@lists.infradead.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).