From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Jiri Slaby" <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
"Frédéric Danis" <frederic.danis.oss@gmail.com>
Subject: Re: [PATCH 0/2] serdev: bus-code clean ups
Date: Tue, 9 Jan 2018 16:48:36 +0100 [thread overview]
Message-ID: <20180109154836.GB10213@kroah.com> (raw)
In-Reply-To: <20180108135014.GA27201@localhost>
On Mon, Jan 08, 2018 at 02:50:14PM +0100, Johan Hovold wrote:
> On Mon, Jan 08, 2018 at 01:42:31PM +0100, Johan Hovold wrote:
> > As noted by Hans, we currently fail to generate uevents for ACPI serdev
> > controller as they do not have any ACPI companions from which ACPI
> > modaliases are constructed.
> >
> > In fact, we should not have been generating modaliases for controllers
> > in the first place as controllers are not bound to drivers.
> >
> > This series applies on top of Hans's minimal fix which suppresses the
> > uevent errors for ACPI controllers (even though it could replace it
> > entirely if preferred).
>
> I somehow forgot to CC Hans. Sorry about that. This series can be found
> here:
>
> https://lkml.kernel.org/r/20180108124233.26729-1-johan@kernel.org
Minor issue found with patch 1, can you fix that up and resend and cc:
him this time? :)
thanks,
greg k-h
prev parent reply other threads:[~2018-01-09 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 12:42 [PATCH 0/2] serdev: bus-code clean ups Johan Hovold
2018-01-08 12:42 ` [PATCH 1/2] serdev: do not generate modaliases for controllers Johan Hovold
2018-01-09 15:48 ` Greg Kroah-Hartman
2018-01-09 15:56 ` Johan Hovold
2018-01-08 12:42 ` [PATCH 2/2] serdev: only match serdev devices Johan Hovold
2018-01-08 13:50 ` [PATCH 0/2] serdev: bus-code clean ups Johan Hovold
2018-01-09 15:48 ` Greg Kroah-Hartman [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=20180109154836.GB10213@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=frederic.danis.oss@gmail.com \
--cc=hdegoede@redhat.com \
--cc=johan@kernel.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
/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.