Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1601627 > unrolled thread
| Started by | Mark Brown <broonie@kernel.org> |
|---|---|
| First post | 2017-03-15 19:30 +0100 |
| Last post | 2017-03-15 19:30 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How to handle quirky behavior with boards. Mark Brown <broonie@kernel.org> - 2017-03-15 19:30 +0100
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Date | 2017-03-15 19:30 +0100 |
| Subject | Re: How to handle quirky behavior with boards. |
| Message-ID | <tllQm-32M-25@gated-at.bofh.it> |
[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 top | Article view | linux.kernel
csiph-web