When does mach-types get updated in a tree?

When does mach-types get updated in a tree?

[John Linn]

> -----Original Message-----
> From: John Linn
> Sent: Wednesday, February 23, 2011 12:06 PM
> To: 'linux-arm-kernel at lists.infradead.org'; 'linux at arm.linux.org.uk'
> Cc: grant.likely at secretlab.ca
> Subject: When does mach-types get updated in a tree?
> 
> I am trying to get a branch ready that could be pulled from with my
new patches.

Maybe I missed it, but I didn't notice any response to this,
or it was a really dumb question that didn't deserve an answer.

I appreciate all the community help (and patience) on my 1st ARM
patches.

I have a new branch ready with patches that's based on the Linus branch
and
Russell's p2v-stable branch.

It won't build without a hack to mach-types so I'm not sure how to
proceed.

Thanks,
John

> 
> There is a new Xilinx entry when I look at the
> http://www.arm.linux.org.uk/developer/machines/download.php.
> 
> But I don't see a Xilinx entry anywhere in any git trees.
> 
> Maybe I overlooked it, or don't really understand the process (more
than likely).
> 
> Thanks,
> John

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

When does mach-types get updated in a tree?

[Russell King - ARM Linux]

On Sat, Feb 26, 2011 at 08:40:24AM -0700, John Linn wrote:
> > -----Original Message-----
> > From: John Linn
> > Sent: Wednesday, February 23, 2011 12:06 PM
> > To: 'linux-arm-kernel at lists.infradead.org'; 'linux at arm.linux.org.uk'
> > Cc: grant.likely at secretlab.ca
> > Subject: When does mach-types get updated in a tree?
> > 
> > I am trying to get a branch ready that could be pulled from with my
> new patches.
> 
> Maybe I missed it, but I didn't notice any response to this,
> or it was a really dumb question that didn't deserve an answer.

I don't update it too frequently because its becoming quite a burden to
edit out all the buggered entries people have made in it - and I don't
want to draw attention to it by updating it too regularly.  I can see
that it's a file that Linus will eventually complain about - it is 134K,
most of which is probably not used.

So I tend to update it on request, and normally no more than once every
two months.

When does mach-types get updated in a tree?

[John Linn]

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Monday, February 28, 2011 3:11 AM
> To: John Linn
> Cc: linux-arm-kernel at lists.infradead.org; grant.likely at secretlab.ca
> Subject: Re: When does mach-types get updated in a tree?
> 
> On Sat, Feb 26, 2011 at 08:40:24AM -0700, John Linn wrote:
> > > -----Original Message-----
> > > From: John Linn
> > > Sent: Wednesday, February 23, 2011 12:06 PM
> > > To: 'linux-arm-kernel at lists.infradead.org';
'linux at arm.linux.org.uk'
> > > Cc: grant.likely at secretlab.ca
> > > Subject: When does mach-types get updated in a tree?
> > >
> > > I am trying to get a branch ready that could be pulled from with
my
> > new patches.
> >
> > Maybe I missed it, but I didn't notice any response to this,
> > or it was a really dumb question that didn't deserve an answer.
> 
> I don't update it too frequently because its becoming quite a burden
to
> edit out all the buggered entries people have made in it - and I don't
> want to draw attention to it by updating it too regularly.  I can see
> that it's a file that Linus will eventually complain about - it is
134K,
> most of which is probably not used.

Thanks for the insight there. 
> 
> So I tend to update it on request, and normally no more than once
every
> two months.

What is your suggestion to people with regards to patches that need the
update?

I'm open to suggestions, just trying to work with everyone the best way
to get
Xilinx patches into the system.

I could submit my patches to your patch system if that helps, or have a
branch
that you can pull from (and it relies on the mach-types update)?

Thanks for your time,
John







This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

When does mach-types get updated in a tree?

[Russell King - ARM Linux]

On Mon, Feb 28, 2011 at 07:35:57AM -0700, John Linn wrote:
> What is your suggestion to people with regards to patches that need the
> update?

The only suggestion I can make is: don't wait until the last minute before
putting something into the machine registry, because you will get into
these kinds of problems.

If I do an update now, it'll be the second time it's happened in February.
It's likely it will need another update just before the merge window too
in 3-4 weeks time.

So really all that I can say is that people need to ensure that they get
stuff from the machine registry earlier rather than later.

I do think we're heading for a major problem with the mach-types file
becoming too big inspite of its brevity.  I think I may start marking
entries as 'inactive' and therefore omitted from the kernel's tree if
they don't appear in mainline within one year of being allocated (or
some similar rule.)

> I'm open to suggestions, just trying to work with everyone the best way
> to get Xilinx patches into the system.

The only thing I can think is to wait a couple more weeks and I'll see
about doing an update mid-March.  Maybe by then we can have a smaller
file...

When does mach-types get updated in a tree?

[John Linn]

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Monday, February 28, 2011 8:11 AM
> To: John Linn
> Cc: linux-arm-kernel at lists.infradead.org; grant.likely at secretlab.ca
> Subject: Re: When does mach-types get updated in a tree?
> 
> On Mon, Feb 28, 2011 at 07:35:57AM -0700, John Linn wrote:
> > What is your suggestion to people with regards to patches that need
the
> > update?
> 
> The only suggestion I can make is: don't wait until the last minute
before
> putting something into the machine registry, because you will get into
> these kinds of problems.

Yes agreed. My fault, lesson learned.

> 
> If I do an update now, it'll be the second time it's happened in
February.
> It's likely it will need another update just before the merge window
too
> in 3-4 weeks time.
> 
> So really all that I can say is that people need to ensure that they
get
> stuff from the machine registry earlier rather than later.
> 
> I do think we're heading for a major problem with the mach-types file
> becoming too big inspite of its brevity.  I think I may start marking
> entries as 'inactive' and therefore omitted from the kernel's tree if
> they don't appear in mainline within one year of being allocated (or
> some similar rule.)
> 

Wouldn't device tree help with this problem?

> > I'm open to suggestions, just trying to work with everyone the best
way
> > to get Xilinx patches into the system.
> 
> The only thing I can think is to wait a couple more weeks and I'll see
> about doing an update mid-March.  Maybe by then we can have a smaller
> file...

Ok, thanks.

-- John


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

When does mach-types get updated in a tree?

[Russell King - ARM Linux]

On Mon, Feb 28, 2011 at 08:34:38AM -0700, John Linn wrote:
> > I do think we're heading for a major problem with the mach-types file
> > becoming too big inspite of its brevity.  I think I may start marking
> > entries as 'inactive' and therefore omitted from the kernel's tree if
> > they don't appear in mainline within one year of being allocated (or
> > some similar rule.)
> > 
> 
> Wouldn't device tree help with this problem?

We'll just end up with a string-space problem instead of a number space
problem.

I don't know how many clashing names we end up with today (because the
machine number allocator explicitly prevents it happening) but I would
not be surprised if there weren't clashes occuring with 3500 names
registered.

Having now done some investigations, this is silly.  About 86% of the
entries in the machine registry are not merged into the kernel.  48%
of the contents of the machine registry refer to platforms registered
more than two years ago but are not merged into mainline.  For four
years, that figure drops to 27%.  For one year, it's 64%.

So, merely implmenting a rule which says that entries which haven't
been merged into mainline within 12 months from the date they were last
updated would cut the file down to about 48K, almost 90K smaller.  I
think that's worth doing.

When does mach-types get updated in a tree?

[Detlef Vollmann]

On 02/28/11 16:49, Russell King - ARM Linux wrote:
>>> I do think we're heading for a major problem with the mach-types file
>>> becoming too big inspite of its brevity.  I think I may start marking
>>> entries as 'inactive' and therefore omitted from the kernel's tree if
>>> they don't appear in mainline within one year of being allocated (or
>>> some similar rule.)

> Having now done some investigations, this is silly.  About 86% of the
> entries in the machine registry are not merged into the kernel.  48%
> of the contents of the machine registry refer to platforms registered
> more than two years ago but are not merged into mainline.  For four
> years, that figure drops to 27%.  For one year, it's 64%.
>
> So, merely implmenting a rule which says that entries which haven't
> been merged into mainline within 12 months from the date they were last
> updated would cut the file down to about 48K, almost 90K smaller.  I
> think that's worth doing.
Hmmm, we have currently two entries registered for CPU modules we
use in a number of internal projects.  Though we're happy to
share the code for these modules, we never intended to propose it
for mainline (as nobody alse can use these modules).
What do you propose for such cases?
Do you have a block of numbers for "private use"?

   Detlef

When does mach-types get updated in a tree?

[John Linn]

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Monday, February 28, 2011 8:11 AM
> To: John Linn
> Cc: linux-arm-kernel at lists.infradead.org; grant.likely at secretlab.ca
> Subject: Re: When does mach-types get updated in a tree?
> 
> On Mon, Feb 28, 2011 at 07:35:57AM -0700, John Linn wrote:
> > What is your suggestion to people with regards to patches that need
the
> > update?
> 
> The only suggestion I can make is: don't wait until the last minute
before
> putting something into the machine registry, because you will get into
> these kinds of problems.
> 
> If I do an update now, it'll be the second time it's happened in
February.
> It's likely it will need another update just before the merge window
too
> in 3-4 weeks time.
> 
> So really all that I can say is that people need to ensure that they
get
> stuff from the machine registry earlier rather than later.
> 
> I do think we're heading for a major problem with the mach-types file
> becoming too big inspite of its brevity.  I think I may start marking
> entries as 'inactive' and therefore omitted from the kernel's tree if
> they don't appear in mainline within one year of being allocated (or
> some similar rule.)
> 
> > I'm open to suggestions, just trying to work with everyone the best
way
> > to get Xilinx patches into the system.
> 
> The only thing I can think is to wait a couple more weeks and I'll see
> about doing an update mid-March.  Maybe by then we can have a smaller
> file...

Hi Russell,

Any chance you'll be able to do the update of mach-types for the merge?

Thanks,
John


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

When does mach-types get updated in a tree?

[Russell King - ARM Linux]

On Tue, Mar 15, 2011 at 08:31:00AM -0600, John Linn wrote:
> Any chance you'll be able to do the update of mach-types for the merge?

That update is now queued.  Thanks for reminding me.

When does mach-types get updated in a tree?

[John Linn]

> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Tuesday, March 15, 2011 3:26 PM
> To: John Linn
> Cc: linux-arm-kernel at lists.infradead.org; grant.likely at secretlab.ca
> Subject: Re: When does mach-types get updated in a tree?
> 
> On Tue, Mar 15, 2011 at 08:31:00AM -0600, John Linn wrote:
> > Any chance you'll be able to do the update of mach-types for the
merge?
> 
> That update is now queued.  Thanks for reminding me.

No problem, appreciate your help.

Any chance of you merging in my patches that we reviewed for Xilinx ARM?

(git://git.xilinx.com/linux-2.6-xlnx, arm-mainline branch)

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

When does mach-types get updated in a tree?

[John Linn]

I am trying to get a branch ready that could be pulled from with my new
patches.

There is a new Xilinx entry when I look at the
http://www.arm.linux.org.uk/developer/machines/download.php.

But I don't see a Xilinx entry anywhere in any git trees.

Maybe I overlooked it, or don't really understand the process (more than
likely).

Thanks,
John

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.