mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: Jeffy Chen <jeffy.chen@rock-chips.com>
Cc: bleung@chromium.org, Olof Johansson <olof@lixom.net>,
	linux-kernel@vger.kernel.org, bleung@google.com
Subject: Re: [PATCH] platform/chrome: cros_ec_dev - Use devm_mfd_add_devices
Date: Mon, 14 Aug 2017 23:47:12 -0700	[thread overview]
Message-ID: <20170815064712.GB100591@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <1502104734-32459-1-git-send-email-jeffy.chen@rock-chips.com>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi Jeffy,

On Mon, Aug 07, 2017 at 07:18:54PM +0800, Jeffy Chen wrote:
> Currently we are calling mfd_add_devices to add devices without matched
> mfd_remove_devices to remove them.
> 
> That would cause warning when re-binding cros_ec_dev:
> 
> [  123.536192] sysfs: cannot create duplicate filename '/bus/platform/devices/cros-
> ec-accel.0'
> [  123.536210] ------------[ cut here ]------------
> [  123.536223] WARNING: CPU: 3 PID: 156 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x
> 84
> [  123.536226] Modules linked in:
> [  123.536236] CPU: 3 PID: 156 Comm: bash Not tainted 4.13.0-rc3-next-20170731 #216
> [  123.536238] Hardware name: Google Kevin (DT)
> [  123.536242] task: ffffffc0f28bab80 task.stack: ffffffc0f1b30000
> [  123.536247] PC is at sysfs_warn_dup+0x68/0x84
> [  123.536251] LR is at sysfs_warn_dup+0x68/0x84
> 
> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>

Thanks for the fix. Applied for v4.14.

Thanks,
Benson

-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-08-15  6:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 11:18 Jeffy Chen
2017-08-15  6:47 ` Benson Leung [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=20170815064712.GB100591@decatoncale.mtv.corp.google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=jeffy.chen@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    /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®