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.