<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/scripts/mod, branch v3.4.95</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/scripts/mod?h=v3.4.95</id>
<link rel='self' href='https://git.amat.us/linux/atom/scripts/mod?h=v3.4.95'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-05-18T12:25:56Z</updated>
<entry>
<title>powerpc: Add vr save/restore functions</title>
<updated>2014-05-18T12:25:56Z</updated>
<author>
<name>Andreas Schwab</name>
<email>schwab@linux-m68k.org</email>
</author>
<published>2013-12-30T14:31:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7dff32efd24849aca3ab1eabe8b867025f34a3f8'/>
<id>urn:sha1:7dff32efd24849aca3ab1eabe8b867025f34a3f8</id>
<content type='text'>
commit 8fe9c93e7453e67b8bd09f263ec1bb0783c733fc upstream.

GCC 4.8 now generates out-of-line vr save/restore functions when
optimizing for size.  They are needed for the raid6 altivec support.

Signed-off-by: Andreas Schwab &lt;schwab@linux-m68k.org&gt;
Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Cc: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Modpost: fixed USB alias generation for ranges including 0x9 and 0xA</title>
<updated>2014-02-22T18:32:46Z</updated>
<author>
<name>Jan Moskyto Matejka</name>
<email>mq@suse.cz</email>
</author>
<published>2014-02-07T18:15:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e7a95613d77dcbcbefe99b465c6488550caf2c85'/>
<id>urn:sha1:e7a95613d77dcbcbefe99b465c6488550caf2c85</id>
<content type='text'>
commit 03b56329f9bb5a1cb73d7dc659d529a9a9bf3acc upstream.

Commit afe2dab4f6 ("USB: add hex/bcd detection to usb modalias generation")
changed the routine that generates alias ranges. Before that change, only
digits 0-9 were supported; the commit tried to fix the case when the range
includes higher values than 0x9.

Unfortunately, the commit didn't fix the case when the range includes both
0x9 and 0xA, meaning that the final range must look like [x-9A-y] where
x &lt;= 0x9 and y &gt;= 0xA -- instead the [x-9A-x] range was produced.

Modprobe doesn't complain as it sees no difference between no-match and
bad-pattern results of fnmatch().

Fixing this simple bug to fix the aliases.
Also changing the hardcoded beginning of the range to uppercase as all the
other letters are also uppercase in the device version numbers.

Fortunately, this affects only the dvb-usb-dib0700 module, AFAIK.

Signed-off-by: Jan Moskyto Matejka &lt;mq@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Merge branch 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild</title>
<updated>2012-04-24T02:45:19Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-04-24T02:45:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4d634ca35a8b38530b134ae92bc9e3cc9c23c030'/>
<id>urn:sha1:4d634ca35a8b38530b134ae92bc9e3cc9c23c030</id>
<content type='text'>
Pull build system failure fix from Michal Marek:
 "This fixes build failure with newer gcc that adds some internal
  symbols that end in "__mod_*_device_table", but are not actually the
  tables themselves."

* 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild:
  Fix modpost failures in fedora 17
</content>
</entry>
<entry>
<title>Fix modpost failures in fedora 17</title>
<updated>2012-04-18T19:42:07Z</updated>
<author>
<name>David Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2012-04-12T18:37:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e88aa7bbbe3046a125ea1936b16bb921cc9c6349'/>
<id>urn:sha1:e88aa7bbbe3046a125ea1936b16bb921cc9c6349</id>
<content type='text'>
The symbol table on x86-64 starts to have entries that have names
like:

_GLOBAL__sub_I_65535_0___mod_x86cpu_device_table

They are of type STT_FUNCTION and this one had a length of 18.  This
matched the device ID validation logic and it barfed because the
length did not meet the device type's criteria.

--------------------
FATAL: arch/x86/crypto/aesni-intel: sizeof(struct x86cpu_device_id)=16 is not a modulo of the size of section __mod_x86cpu_device_table=18.
Fix definition of struct x86cpu_device_id in mod_devicetable.h
--------------------

These are some kind of compiler tool internal stuff being emitted and
not something we want to inspect in modpost's device ID table
validation code.

So skip the symbol if it is not of type STT_OBJECT.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Acked-by: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>modpost: Fix modpost license checking of vmlinux.o</title>
<updated>2012-04-10T03:52:56Z</updated>
<author>
<name>Frank Rowand</name>
<email>frank.rowand@am.sony.com</email>
</author>
<published>2012-04-10T00:59:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=258f742635360175564e9470eb060ff4d4b984e7'/>
<id>urn:sha1:258f742635360175564e9470eb060ff4d4b984e7</id>
<content type='text'>
Commit f02e8a6596b7 ("module: Sort exported symbols") sorts symbols
placing each of them in its own elf section.  This sorting and merging
into the canonical sections are done by the linker.

Unfortunately modpost to generate Module.symvers file parses vmlinux.o
(which is not linked yet) and all modules object files (which aren't
linked yet).  These aren't sanitized by the linker yet.  That breaks
modpost that can't detect license properly for modules.

This patch makes modpost aware of the new exported symbols structure.

[ This above is a slightly corrected version of the explanation of the
  problem, copied from commit 62a2635610db ("modpost: Fix modpost's
  license checking V3").  That commit fixed the problem for module
  object files, but not for vmlinux.o.  This patch fixes modpost for
  vmlinux.o. ]

Signed-off-by: Frank Rowand &lt;frank.rowand@am.sony.com&gt;
Signed-off-by: Alessio Igor Bogani &lt;abogani@kernel.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild</title>
<updated>2012-03-31T01:15:43Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-03-31T01:15:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=923f79743c76583ed4684e2c80c8da51a7268af3'/>
<id>urn:sha1:923f79743c76583ed4684e2c80c8da51a7268af3</id>
<content type='text'>
Pull kbuild changes from Michal Marek:
 - Unification of cmd_uimage among archs that use it
 - make headers_check tries harder before reporting a missing
   &lt;linux/types.h&gt; include
 - kbuild portability fix for shells that do not support echo -e
 - make clean descends into samples/
 - setlocalversion grep fix
 - modpost typo fix
 - dtc warnings fix

* 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild:
  setlocalversion: Use "grep -q" instead of piping output to "read dummy"
  modpost: fix ALL_INIT_DATA_SECTIONS
  Kbuild: centralize MKIMAGE and cmd_uimage definitions
  headers_check: recursively search for linux/types.h inclusion
  scripts/Kbuild.include: Fix portability problem of "echo -e"
  scripts: dtc: fix compile warnings
  kbuild: clean up samples directory
  kbuild: disable -Wmissing-field-initializers for W=1
</content>
</entry>
<entry>
<title>modpost: fix ALL_INIT_DATA_SECTIONS</title>
<updated>2012-03-26T20:39:52Z</updated>
<author>
<name>Jan Beulich</name>
<email>JBeulich@suse.com</email>
</author>
<published>2012-03-08T09:41:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9aaf440f8fabcebf9ea79a62ccf4c212e6544b49'/>
<id>urn:sha1:9aaf440f8fabcebf9ea79a62ccf4c212e6544b49</id>
<content type='text'>
This was lacking a comma between two supposed to be separate strings.

Signed-off-by: Jan Beulich &lt;jbeulich@suse.com&gt;
Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>Merge 3.3-rc6 into driver-core-next</title>
<updated>2012-03-09T20:35:53Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-03-09T20:35:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=263a5c8e16c34199ddf6de3f102e789ffa3ee26e'/>
<id>urn:sha1:263a5c8e16c34199ddf6de3f102e789ffa3ee26e</id>
<content type='text'>
This was done to resolve a conflict in the drivers/base/cpu.c file.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mod/file2alias: make modpost compile on darwin again</title>
<updated>2012-02-26T23:59:31Z</updated>
<author>
<name>Andreas Bießmann</name>
<email>andreas@biessmann.de</email>
</author>
<published>2012-02-24T07:23:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dd2a3acaecd7abb2d43b09a823cf2e4c967fa2ac'/>
<id>urn:sha1:dd2a3acaecd7abb2d43b09a823cf2e4c967fa2ac</id>
<content type='text'>
commit e49ce14150c64b29a8dd211df785576fa19a9858 breaks cross compiling
the linux kernel on darwin hosts.
This fix introduce some minimal glue to adopt linker section handling
for darwin hosts.

Signed-off-by: Andreas Bießmann &lt;andreas@biessmann.de&gt;
CC: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
CC: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
CC: Jochen Friedrich &lt;jochen@scram.de&gt;
CC: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
CC: "K. Y. Srinivasan" &lt;kys@microsoft.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Tested-by: Bernhard Walle &lt;bernhard@bwalle.de&gt;
</content>
</entry>
<entry>
<title>ARM: 7324/1: modpost: Fix section warnings for ARM for many compilers</title>
<updated>2012-02-15T11:04:36Z</updated>
<author>
<name>Tony Lindgren</name>
<email>tony@atomide.com</email>
</author>
<published>2012-02-14T20:58:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6e2e340b59d2d4e7b6b7f2c2d02b0d5ca4df6458'/>
<id>urn:sha1:6e2e340b59d2d4e7b6b7f2c2d02b0d5ca4df6458</id>
<content type='text'>
It turns out that many compilers don't show section warnings on ARM
currently because handling for ARM_CALL relocs are missing from
modpost.c.

Based on commit c2e26114 ([ARM] 3205/1: Handle new EABI relocations when
loading kernel modules) it seems that R_ARM_PC24, R_ARM_CALL and
R_ARM_JUMP24 can be handled the same way.

Note that at least Debian libc6-dev is missing defines for both
R_ARM_CALL and R_ARM_JUMP24 in /usr/include/elf.h. So for now
we need to define them in modpost.c if not defined.

Acked-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Cc: Anders Kaseorg &lt;andersk@ksplice.com&gt;
Cc: Greg KH &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
</feed>
