<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/arch/ia64/scripts, branch v2.6.31.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/arch/ia64/scripts?h=v2.6.31.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/arch/ia64/scripts?h=v2.6.31.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-03-26T17:50:09Z</updated>
<entry>
<title>ia64/pv_ops/pvchecker: support mov = ar.itc paravirtualization</title>
<updated>2009-03-26T17:50:09Z</updated>
<author>
<name>Isaku Yamahata</name>
<email>yamahata@valinux.co.jp</email>
</author>
<published>2009-03-04T12:05:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9d1964f25c3c43dab5a5f4761477bcfc8402250e'/>
<id>urn:sha1:9d1964f25c3c43dab5a5f4761477bcfc8402250e</id>
<content type='text'>
add suport for mov = ar.itc to pvchecker.

Signed-off-by: Isaku Yamahata &lt;yamahata@valinux.co.jp&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>ia64/pv_ops: paravirtualized instruction checker.</title>
<updated>2008-10-17T17:12:54Z</updated>
<author>
<name>Isaku Yamahata</name>
<email>yamahata@valinux.co.jp</email>
</author>
<published>2008-10-17T02:18:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f8d1f99f3958c46cdc983743d75d0b31b9accb80'/>
<id>urn:sha1:f8d1f99f3958c46cdc983743d75d0b31b9accb80</id>
<content type='text'>
This patch implements a checker to detect instructions which
should be paravirtualized instead of direct writing raw instruction.
This patch does rough check so that it doesn't fully cover all cases,
but it can detects most cases of paravirtualization breakage of hand
written assembly codes.

Signed-off-by: Isaku Yamahata &lt;yamahata@valinux.co.jp&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>[IA64] don't assume that unwcheck.py is executable</title>
<updated>2007-12-07T22:42:08Z</updated>
<author>
<name>Andrew Morton</name>
<email>akpm@linux-foundation.org</email>
</author>
<published>2007-12-07T22:42:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ff08e657f3e7224d090dd816e00cea2c110575c4'/>
<id>urn:sha1:ff08e657f3e7224d090dd816e00cea2c110575c4</id>
<content type='text'>
Don't assume that this file has execute permissions.  For example, patch(1)
loses that information.

Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>[IA64] check-segrel.lds vs --build-id</title>
<updated>2007-10-29T17:53:04Z</updated>
<author>
<name>Roland McGrath</name>
<email>roland@redhat.com</email>
</author>
<published>2007-10-18T19:54:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d650c37b2f8dbc5ac5055957617816eeb40ec79c'/>
<id>urn:sha1:d650c37b2f8dbc5ac5055957617816eeb40ec79c</id>
<content type='text'>
Some versions of ld with --build-id support will crash when using the flag
with a linker script that discards notes.  This bites ia64's check-segrel.lds.
The bug is easy to avoid.

Signed-off-by: Roland McGrath &lt;roland@redhat.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@ppc970.osdl.org</email>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
