Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <1523224627-24136-1-git-send-email-aspriel@gmail.com>
References: <1523224627-24136-1-git-send-email-aspriel@gmail.com>
From:   Arend van Spriel <aspriel@gmail.com>
Date:   Wed, 18 Apr 2018 21:11:23 +0200
Message-ID: <CAJ65rDwOCGZL+=jJj-4-HjPVpR8EhZSS5x5ACS_3aC3gwpUxmA@mail.gmail.com>
Subject: Re: [RESEND PATCH] drivers: change struct device_driver::coredump()
 return type to void
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        Brian Norris <briannorris@chromium.org>,
        Arend van Spriel <aspriel@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Apr 8, 2018 at 11:57 PM, Arend van Spriel <aspriel@gmail.com> wrote:
> Upon submitting a patch for mwifiex [1] it was discussed whether this
> callback function could fail. To keep things simple there is no need
> for the error code so the driver can do the task synchronous or not
> without worries. Currently the device driver core already ignores the
> return value so changing it to void.
>
> [1] https://patchwork.kernel.org/patch/10231933/
>
> Signed-off-by: Arend van Spriel <aspriel@gmail.com>
> ---
> Hi Greg,
>
> Here is a resend of my patch that got lost. See if it makes it
> this time ;-)

Hi Greg,

Your patch-bot replied to this one and I may be overly anxious, but
that's because things ran haywire in the initial submission. So is the
patch in your queue for 4.17?

Regards,
Arend

> Regards,
> Arend
> ---
>  include/linux/device.h | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)