- Pull in 2.6.37-rc1-git10 snapshot
- SECURITY_DMESG_RESTRICT added, the principle of least surprise dictates
we should probably have it off. If you want to restrict dmesg access
you may use the kernel.dmesg_restrict sysctl.
- linux-2.6-bluetooth-autosuspend.patch: merged upstream.
kernel.src:2188: W: macro-in-%changelog %released_kernel
kernel.src:2232: W: macro-in-%changelog %verify
kernel.src:2411: W: macro-in-%changelog %{expand
(Packagers should avoid using macros in changelog items, but this is a minor
error. The easy fix here is to %% comment out any macros in changelog entries,
to prevent unexpected and random behavior.)
kernel.src:386: W: macro-in-comment %nobuildarches
kernel.src:432: W: macro-in-comment %post
kernel.src:1002: W: macro-in-comment %{vanillaversion}
kernel.src:1003: W: macro-in-comment %{kversion}
kernel.src:1005: W: macro-in-comment %{kversion}
kernel.src:1883: W: macro-in-comment %{image_install_path}
(Packagers should avoid using macros in comments, but this is a minor error.
The easy fix here is to %% comment out any macros in comments, to prevent
unexpected and random behavior.)
(This is coming from line 445: Provides: kernel =
%{rpmversion}-%{pkg_release}\.
I don't see any reason for this line, as rpm is autoproviding kernel =
%{version}-%{release} (and %{version} is being set to %{rpmversion} and
%{release} is being set to %{pkg_release}.)
kernel.src:2188: W: macro-in-%changelog %released_kernel
kernel.src:2232: W: macro-in-%changelog %verify
kernel.src:2411: W: macro-in-%changelog %{expand
(Packagers should avoid using macros in changelog items, but this is a minor
error. The easy fix here is to %% comment out any macros in changelog entries,
to prevent unexpected and random behavior.)
