Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1601627

Re: How to handle quirky behavior with boards.

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject Re: How to handle quirky behavior with boards.
Date 2017-03-15 19:30 +0100
Message-ID <tllQm-32M-25@gated-at.bofh.it> (permalink)
References <tgcXn-3Po-19@gated-at.bofh.it> <tgXCW-3fA-23@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Fri, Mar 03, 2017 at 04:31:43PM +0100, Olliver Schinagl wrote:

> So my question is, what is there against moving some of the constrants
> before the always-on, so that the enable can atleast function properly
> according to its parameters?

No, and in general please don't ask to send patches - just send patches
with any explanation/discussion in the cover letter and/or commit log.
That tends to make things go faster as the code can make any issues more
obvious and if there's no problem then patches can just be applied
immediately.

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: How to handle quirky behavior with boards. Mark Brown <broonie@kernel.org> - 2017-03-15 19:30 +0100

csiph-web