Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751503AbcDZEzG (ORCPT ); Tue, 26 Apr 2016 00:55:06 -0400 Received: from mail-io0-f179.google.com ([209.85.223.179]:33001 "EHLO mail-io0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750869AbcDZEzE (ORCPT ); Tue, 26 Apr 2016 00:55:04 -0400 MIME-Version: 1.0 In-Reply-To: <1459964260-43054-1-git-send-email-s-anna@ti.com> References: <1459964260-43054-1-git-send-email-s-anna@ti.com> Date: Tue, 26 Apr 2016 05:55:02 +0100 Message-ID: Subject: Re: [PATCH 0/4] OMAP Mailbox legacy platform device support removal From: Jassi Brar To: Suman Anna Cc: Linux Kernel Mailing List , linux-omap Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 695 Lines: 21 On Wed, Apr 6, 2016 at 6:37 PM, Suman Anna 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.