From: Suman Anna <s-anna@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/4] OMAP Mailbox legacy platform device support removal
Date: Wed, 6 Apr 2016 12:37:36 -0500 [thread overview]
Message-ID: <1459964260-43054-1-git-send-email-s-anna@ti.com> (raw)
Hi Jassi,
This series cleans up the OMAP Mailbox driver dropping the
support for legacy non-DT platform devices. The infrastructure
for creating any such devices has all been cleaned up from the
mach-omap2 layers.
The removal from the driver is accomplished in patch 1, while the
remaining patches do some minor checkpatch fixes.
Patches baselined on 4.6-rc2.
regards
Suman
Suman Anna (4):
mailbox/omap: drop legacy platform device support
mailbox/omap: use variable name for sizeof() operator
mailbox/omap: remove FSF mailing address paragraph
mailbox/omap: add blank lines after declarations
drivers/mailbox/omap-mailbox.c | 116 ++++++++++++-----------------
include/linux/platform_data/mailbox-omap.h | 58 ---------------
2 files changed, 48 insertions(+), 126 deletions(-)
delete mode 100644 include/linux/platform_data/mailbox-omap.h
--
2.7.4
next reply other threads:[~2016-04-06 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 17:37 Suman Anna [this message]
2016-04-06 17:37 ` [PATCH 1/4] mailbox/omap: drop legacy platform device support Suman Anna
2016-04-06 17:37 ` [PATCH 2/4] mailbox/omap: use variable name for sizeof() operator Suman Anna
2016-04-06 17:37 ` [PATCH 3/4] mailbox/omap: remove FSF mailing address paragraph Suman Anna
2016-04-06 17:37 ` [PATCH 4/4] mailbox/omap: add blank lines after declarations Suman Anna
2016-04-26 4:55 ` [PATCH 0/4] OMAP Mailbox legacy platform device support removal Jassi Brar
2016-04-26 17:06 ` Suman Anna
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=1459964260-43054-1-git-send-email-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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
all inboxes | Powered by JetHome®