From: Mark Brown <broonie@kernel.org>
To: Michal Suchanek <hramrach@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver
Date: Fri, 1 Jul 2016 18:22:28 +0200 [thread overview]
Message-ID: <20160701162228.GZ6247@sirena.org.uk> (raw)
In-Reply-To: <CAOMqctSfDKJRYf7bY7pz7LE9obUxMvV-v=Ntz3_mk0WGMKbPtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Fri, Jul 01, 2016 at 05:37:53PM +0200, Michal Suchanek wrote:
> Can you, please, specify what problems this patch creates for other users
> and maintainability?
To repeat yet again a major design goal for DT is to describe the
hardware rather than implementation details of the software you plan to
run on the system. Not doing this breaks upgrades or changes in our
ideas of how we control a given bit of hardware.
> Without stating the problems of this solution clearly or proposing alternate
> workable solution there is not much that can be done.
You are rejecting out of hand any suggestion that is not the one
solution you are demanding.
I'm done with this thread, please come back with new code that fits in
with the device model and device tree designs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-01 16:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 19:02 [PATCH v2 0/3] Updated spidev usability patchset Michal Suchanek
2016-06-27 19:02 ` [PATCH v2 1/3] spi: spidev: fix the check for spidev in dt Michal Suchanek
2016-06-27 20:36 ` Mark Brown
2016-06-27 19:02 ` [PATCH v2 2/3] spi: of: allow instantiating slaves without a driver Michal Suchanek
2016-06-27 21:14 ` Mark Brown
2016-06-27 19:02 ` [PATCH v2 3/3] drivers core: allow id match override when manually binding driver Michal Suchanek
2016-06-27 19:09 ` Greg Kroah-Hartman
2016-06-27 19:40 ` Michal Suchanek
2016-06-27 20:32 ` Mark Brown
2016-06-27 22:12 ` Greg Kroah-Hartman
2016-06-28 12:40 ` Michal Suchanek
2016-06-28 15:51 ` Mark Brown
2016-06-28 16:24 ` Michal Suchanek
2016-06-28 18:38 ` Mark Brown
2016-06-28 20:02 ` Michal Suchanek
2016-06-28 20:57 ` Mark Brown
2016-06-29 3:32 ` Michal Suchanek
2016-06-29 18:02 ` Mark Brown
2016-06-30 7:47 ` Michal Suchanek
2016-06-30 9:03 ` Dan O'Donovan
2016-07-01 9:36 ` Mark Brown
2016-07-01 10:11 ` Michal Suchanek
2016-07-01 8:25 ` Mark Brown
2016-07-01 8:58 ` Michal Suchanek
2016-07-01 15:00 ` Mark Brown
2016-07-01 15:37 ` Michal Suchanek
2016-07-01 16:22 ` Mark Brown [this message]
2016-07-01 18:56 ` Michal Suchanek
2016-07-01 19:36 ` Michal Suchanek
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=20160701162228.GZ6247@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hramrach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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 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®