linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/4] OMAP Mailbox legacy platform device support removal
Date: Tue, 26 Apr 2016 12:06:42 -0500	[thread overview]
Message-ID: <571FA022.9010207@ti.com> (raw)
In-Reply-To: <CABb+yY3bsVu9DNwhdCNyan1RH-REjmCWqXP2jvMqpYd-kQaa=g@mail.gmail.com>

On 04/25/2016 11:55 PM, Jassi Brar wrote:
> On Wed, Apr 6, 2016 at 6:37 PM, Suman Anna <s-anna@ti.com> wrote:
>> 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.
>>
> Applied this and the next patchset, with a trivial cleanup
> 
> - #define MBOX_INTR_CFG_TYPE1            (0)
> - #define MBOX_INTR_CFG_TYPE2            (1)
> + #define MBOX_INTR_CFG_TYPE1            0
> + #define MBOX_INTR_CFG_TYPE2            1
> 
> Thanks.

Thanks Jassi.

regards
Suman

      reply	other threads:[~2016-04-26 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 17:37 [PATCH 0/4] OMAP Mailbox legacy platform device support removal Suman Anna
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 [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=571FA022.9010207@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;
as well as URLs for NNTP newsgroup(s).