On Thu, Nov 15, 2018 at 6:42 PM Rob Herring wrote:
>
> On Wed, Nov 14, 2018 at 1:39 PM jonsm...@gmail.com wrote:
> >
> > On Fri, Apr 20, 2018 at 9:36 PM Rob Herring wrote:
> > > I share the concern as I doubt most kernel developers don't know
> > > j
s is that as they evolve and enforce
commonality among driver implementation it will become possible to
turn those in-common pieces into driver libraries.
--
Jon Smirl
jonsm...@gmail.com
ents" in the first place? That seems way out of
> scope for a code of conduct arbitration scheme. Even attempting to
> counsel people as to whether or not they should report incidents can
> get you in trouble in many parts of the world.
>
Which is why the lawyers need to go over this document and I haven't
seen anything posted from them. In the same vein Mauro is concerned
that the way this is code is written it is a binding contract in
Brazil.
> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.mykleb...@hammerspace.com
>
>
--
Jon Smirl
jonsm...@gmail.com
t situation he was initially attacked by external
parties. I will keep recommending that the legal community weigh in
before making this official policy. We are focusing on the case of the
random individual, but I suspect the problem lies in an attack on the
leadership.
>
> I believe that in the vast majority of cases, the TAB will end up
> performing a mediator role to smooth hurt feelings and remind and encourage
> improved communication - very similar to what we've done in the past. I
> really
> believe that bans will continue to be very few and far between, as they have
> been historically (I can only think of 3 in the past decade.)
> -- Tim
>
> ___
> Ksummit-discuss mailing list
> ksummit-disc...@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
--
Jon Smirl
jonsm...@gmail.com
o redo the patch series with
> that.
>
> James
>
>
> > would make this clear and ameliorate the concerns from many people
> > about the open questions we still have, at least for now. This would
> > give us the time to discuss all the details properly and wit
y have to field judicial
> reviews and other challenges. That means the TAB needs to have
> exemplary record keeping and process because anyone who stands up in a
> legal challenge and says 'Umm.. we read it and talked about it and kind
> of decided X but I don't remember why and there are no minutes and there
> is on process document' is going to get fried. Someone needs to have that
> process in place well in advance.
>
> Alan
--
Jon Smirl
jonsm...@gmail.com
On Mon, Sep 24, 2018 at 1:43 PM Max Filippov wrote:
>
> On Fri, Sep 21, 2018 at 5:24 PM, jonsm...@gmail.com
> wrote:
> > On Fri, Sep 21, 2018 at 8:05 PM Joey Pabalinas
> > wrote:
> >> On Fri, Sep 21, 2018 at 07:31:05PM -0400, jonsm...@gmail.com wrote:
> >
On Fri, Sep 21, 2018 at 8:05 PM Joey Pabalinas wrote:
>
> On Fri, Sep 21, 2018 at 07:31:05PM -0400, jonsm...@gmail.com wrote:
> > On Fri, Sep 21, 2018 at 7:17 PM Theodore Y. Ts'o wrote:
> > >
> > > People can decide who they want to respond to, but I'm g
m all sides that are wanting to "help".
> But I hope that it is obvious that the above text is *not* *helpful*.
> Mark, please stop.
>
> - Ted
--
Jon Smirl
jonsm...@gmail.com
New version that adds better support for the A10 plus it fixes an
issue in the previous version.
Note that the A10 does not support the 24Mhz bypass mode.
--
Jon Smirl
jonsm...@gmail.com
pwm
Description: Binary data
l and Android engineering
> http://free-electrons.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Jon Smirl
jonsm...@gmail.com
pwm
Description: Binary data
it, send
an email to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Jon Smirl
jonsm...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ke
error path in apply_microcode_amd()
>
> Trond Myklebust (6):
> LOCKD: Don't call utsname()->nodename from nlmclnt_setlockargs
> SUNRPC: Don't auto-disconnect from the local rpcbind socket
> SUNRPC: If the rpcbind channel is disconnected, fail the call to
&
On Thu, Aug 1, 2013 at 9:34 AM, jonsm...@gmail.com wrote:
> On Thu, Aug 1, 2013 at 6:18 AM, David Woodhouse wrote:
>> On Wed, 2013-07-31 at 17:26 -0400, jonsm...@gmail.com wrote:
>>> Alternatively you may be of the belief that it is impossible to get
>>> rid of the b
On Thu, Aug 1, 2013 at 6:18 AM, David Woodhouse wrote:
> On Wed, 2013-07-31 at 17:26 -0400, jonsm...@gmail.com wrote:
>> Alternatively you may be of the belief that it is impossible to get
>> rid of the board specific code. But x86 doesn't have any of it, why
>> shou
On Wed, Jul 31, 2013 at 4:48 PM, Russell King - ARM Linux
wrote:
> On Wed, Jul 31, 2013 at 04:37:36PM -0400, jonsm...@gmail.com wrote:
>> On Wed, Jul 31, 2013 at 4:14 PM, Russell King - ARM Linux
>> wrote:
>> > However, if we go back to the idea that DT is supposed to de
up to reality - we have USERS of this stuff over the last two
> years. It's found its way into products. If we're going to keep this
> stuff "unstable" then we are actively _hurting_ our users.
>
> I'll say it again: if a binding has been in a final kernel, it is
d be handled as plugins to the checks mechanism -
> basically we'd have a validate_schemas() check function.
>
> I also think we should consider the option of having a simple and
> straightforward schema language which handles, say, 80% of cases with
> a fall back to C for the 2
g run in deferred probing. I
suspect potential savings (if there even is any) are under a
millisecond.
>
> you are just trading one side of the problem for the other.
>
> David Lang
--
Jon Smirl
jonsm...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe l
On Sun, Jul 28, 2013 at 11:35 AM, Richard Cochran
wrote:
> On Sun, Jul 28, 2013 at 10:09:57AM -0400, jonsm...@gmail.com wrote:
>>
>> 3.z kernel is free to alter the schema. But it will have to supply the
>> necessary quirks needed to keep those old dtb's functioning.
hat this kind of
> solutions is good, as I'm not convinced either. That's why we are
> discussing this.
>
> Best regards,
> Tomasz
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kerne
>
> g.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
ple don't do everything correctly from
> the start, this is what the whole staging vs stable topic is about.
>
> Best regards,
> Tomasz
>
>
> ___
> linux-arm-kernel mailing list
> linux-arm-ker...@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Jon Smirl
jonsm...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Fri, Jul 26, 2013 at 10:21 AM, Russell King - ARM Linux
wrote:
> On Fri, Jul 26, 2013 at 10:14:32AM -0400, jonsm...@gmail.com wrote:
>> Yes, yes - that's why the schema should be written down and used as a
>> validation input to dtc. Then dtc can spit out errors for n
ess in the thread would go away if the schema
was written down and discussed. The rule going forward would be no new
nodes that aren't part of the standard schema.
>
> --
> dwmw2
>
> _______
> linux-arm-kernel mailing list
> linux-arm-ker...
validate the
trees it compiles against it issuing warnings for 'non-standard'
usage. Over time the schema would be updated to allow these usages
when everyone agrees to it. Note that there would be a single schema
describing all possible legal Linux device trees.
The scheme is also quite
eed
the cost of joining. The net result will likely be a reduction in the
amount they need to spend on in-house development since they will
learn how to better leverage other developer's work.
--
Jon Smirl
jonsm...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe lin
On Wed, Jun 5, 2013 at 7:26 PM, luke.leighton wrote:
> On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com
> wrote:
>> On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton
>> wrote:
>>> On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström
>>> wrote:
>>>
>
On Wed, Jun 5, 2013 at 7:26 PM, luke.leighton wrote:
> On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com
> wrote:
>> On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton
>> wrote:
>>> On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström
>>> wrote:
>>>
>
l on
your machine. It is called dtc. Check out scripts/dtc.
So if you are in love with fex syntax write a script that converts it
into device tree syntax. Then compile the DTS using dtc into a DTB.
When the DTB is in memory it is a FDT (flattened device tree). It's
that FDT format in m
tsold-intel-qualcomm-in-tablet-processors-in-2012
> [*1] - fex guide for SoCs up to but excluding the Allwinner A20
> http://linux-sunxi.org/Fex_Guide
> [*2] http://lists.phcomp.co.uk/pipermail/arm-netbook/2013-June/007619.html and
> http://lists.phcomp.co.uk/pipermail/arm-netbook/201
On Thu, Dec 27, 2012 at 11:46 AM, anish kumar
wrote:
> On Thu, 2012-12-27 at 11:22 -0500, jonsm...@gmail.com wrote:
>> On Thu, Dec 27, 2012 at 3:27 AM, Woody Wu wrote:
>> > Hi, list
>> >
>> > I know this might be a very basic question. But I really don
o majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Jon Smirl
jonsm...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
33 matches
Mail list logo
