All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-m68k@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH] m68k/gpio: remove arch specific sysfs bus device
Date: Thu, 7 Apr 2016 05:31:14 +1000	[thread overview]
Message-ID: <57056402.8020308@uclinux.org> (raw)
In-Reply-To: <CACRpkda6SHJC-TfeakPa=ZcYtTyhNijN3H6y8FUDyziVNXCEEw@mail.gmail.com>

On 06/04/16 16:57, Linus Walleij wrote:
> On Wed, Apr 6, 2016 at 4:32 AM, Greg Ungerer <gerg@uclinux.org> wrote:
>
>> From: Greg Ungerer <gerg@gumby.(none)>
>>
>> The ColdFire architecture specific gpio support code registers a sysfs
>> bus device named "gpio". This clashes with the new generic API device
>> added in commit 3c702e99 ("gpio: add a userspace chardev ABI for GPIOs").
>>
>> The old ColdFire sysfs gpio device was never used for anything specific,
>> and no links or other nodes were created under it. The new API sysfs gpio
>> device has all the same default sysfs links (device, drivers, etc) and
>> they are properly populated.
>>
>> Remove the old ColdFire sysfs gpio registration.
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>

Thanks Linus. I will push via the m68knommu git tree.

Regards
Greg

      reply	other threads:[~2016-04-06 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  2:32 [PATCH] m68k/gpio: remove arch specific sysfs bus device Greg Ungerer
2016-04-06  6:57 ` Linus Walleij
2016-04-06 19:31   ` Greg Ungerer [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=57056402.8020308@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux@roeck-us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.