Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: nuno.sa@analog.com, Jonathan.Cameron@huawei.com, Stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iio: adis16480: Add debugfs_reg_access entry" failed to apply to 4.14-stable tree
Date: Sun, 15 Dec 2019 13:07:08 -0500	[thread overview]
Message-ID: <20191215180708.GI18043@sasha-vm> (raw)
In-Reply-To: <15764021987748@kroah.com>

On Sun, Dec 15, 2019 at 10:29:58AM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.14-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 4c35b7a51e2f291471f7221d112c6a45c63e83bc Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Nuno=20S=C3=A1?= <nuno.sa@analog.com>
>Date: Mon, 28 Oct 2019 17:33:49 +0100
>Subject: [PATCH] iio: adis16480: Add debugfs_reg_access entry
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>The driver is defining debugfs entries by calling
>`adis16480_debugfs_init()`. However, those entries are attached to the
>iio_dev debugfs entry which won't exist if no debugfs_reg_access
>callback is provided.
>
>Fixes: 2f3abe6cbb6c ("iio:imu: Add support for the ADIS16480 and similar IMUs")
>Signed-off-by: Nuno Sá <nuno.sa@analog.com>
>Cc: <Stable@vger.kernel.org>
>Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

Trivial context conflicts, I've fixed it up and queued for 4.14-4.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2019-12-15 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  9:29 FAILED: patch "[PATCH] iio: adis16480: Add debugfs_reg_access entry" failed to apply to 4.14-stable tree gregkh
2019-12-15 18:07 ` Sasha Levin [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=20191215180708.GI18043@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Stable@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=nuno.sa@analog.com \
    /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