similar to: Section mismatch in parainstructions

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

Thank you for your answer, Kevin. 2. OK, I understand. 1. I checked colon dirs, and indeed they don't have openSUSE_Leap_42.2 dirs directly. But they have different subdirs which have openSUSE_Leap_42.2 dirs. What would be the correct filter set to mirror all openSUSE_Leap_42.2 dirs at any level if I don't want to include all dirs at the root level? At the roor level tehre are many dirs

Dear Kevin: ~ 1 year ago your answer helped me to solve my problem. This time I would like to do a similar thing but little bit modified. I read again carefully INCLUDE/EXCLUDE PATTERN RULES section of rsync manual but still cannot comprehend every part of it. I understand I have to add include patterns first and exclude patterns second. But it is not clear if I have to add all the include

Revert the following 9 commits: [1] 5bdcd510c2ac ("x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs") This was partially reverted because it made good cleanups irrespective of the inlining issue; the error message is still unneeded, and the conversion to STATIC_BRANCH_{NOP,JUMP} should be kept. [2] d5a581d84ae6 ("x86/cpufeature:

I recently replaced a 8600 GT with the above card on openSUSE Tumbleweed x86_64. The screen now flickers and when I change desktops it takes a some 10 to 15 seconds to display the new windows. e.g if I change from desktop 1 (konsole) to desktop 8 (thunderbird) it switches but konsole is displayed for 10 to 15 seconds before thunderbird appears. Occasionally the screen flickers wildly before

Revert the following commits: - 5bdcd510c2ac9efaf55c4cbd8d46421d8e2320cd ("x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs") - d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2 ("x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs") - 0474d5d9d2f7f3b11262f7bf87d0e7314ead9200. ("x86/extable: Macrofy inline assembly

Revert the following commits: - 5bdcd510c2ac9efaf55c4cbd8d46421d8e2320cd ("x86/jump-labels: Macrofy inline assembly code to work around GCC inlining bugs") - d5a581d84ae6b8a4a740464b80d8d9cf1e7947b2 ("x86/cpufeature: Macrofy inline assembly code to work around GCC inlining bugs") - 0474d5d9d2f7f3b11262f7bf87d0e7314ead9200. ("x86/extable: Macrofy inline assembly

Thanks to Andrew for pointing these out. This patch moves the parvirtprobe section into .init.data: it's only used in very very early boot, and for similar reasons, puts lguest_maybe_init and lguest_memory_setup in init.text. As well as fixing some warnings, this frees up a tiny bit more memory. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r ecec388180b2

Thanks to Andrew for pointing these out. This patch moves the parvirtprobe section into .init.data: it's only used in very very early boot, and for similar reasons, puts lguest_maybe_init and lguest_memory_setup in init.text. As well as fixing some warnings, this frees up a tiny bit more memory. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r ecec388180b2

Hi Well it is well some time that my last DUNDI peer has become unreachable. I guess too many issues with spoofed numbers etc. But I am wondering, do people, especially larger entities like telcos, still use DUNDI? I know that in some Hamradio communities, DUNDI is used to interconnect PBXes, but that is with private phone number ranges, not connected to the public. Want some DUNDI peering?

Hi Andi, Here's a little batch of cleanups: - re-enable VDSO when PARAVIRT is enabled - make the parainstructions symbols match the other altinstructions naming convention - add kernel command-line options to disable altinstructions for smp and pv_ops Oh, and I'm mailing your noreplacement patch back at you, for no particularly good reason. J --

Hi Andi, Here's a little batch of cleanups: - re-enable VDSO when PARAVIRT is enabled - make the parainstructions symbols match the other altinstructions naming convention - add kernel command-line options to disable altinstructions for smp and pv_ops Oh, and I'm mailing your noreplacement patch back at you, for no particularly good reason. J --

This is a small series getting rid of paravirt patching by switching completely to alternative patching for the same functionality. The basic idea is to add the capability to switch from indirect to direct calls via a special alternative patching option. This removes _some_ of the paravirt macro maze, but most of it needs to stay due to the need of hiding the call instructions from the compiler

This is a small series getting rid of paravirt patching by switching completely to alternative patching for the same functionality. The basic idea is to add the capability to switch from indirect to direct calls via a special alternative patching option. This removes _some_ of the paravirt macro maze, but most of it needs to stay due to the need of hiding the call instructions from the compiler

Building zaptel-1.4 from today's svn against kernel 2.6.25-git2: ............ Building modules, stage 2. MODPOST 13 modules WARNING: modpost: Found 1 section mismatch(es). ........ The other warnings were about "BIT" redefined, which I assume are benign. Should I worry? If so, what do I do? sean

On 31/12/13 10:36, Ilia Mirkin wrote: > On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce <sboyce at blueyonder.co.uk> wrote: >> System x86_64 with openSUSE 13.1. >> X.Org version: 1.14.99.905 >> >> openSUSE 12.2 kernels boot successfully into a graphical screen, login to >> KDE4, etc. all normal. >> >> 3.13-rc kernels boot fully with X running but no

I don't think the numbered patch scheme we're using in the paravirtops patch series is going to work very well. It assumes that we've got the patch order of all the existing patches right, and that we don't need to fit in any new patches between them. I think we'll need the flexibility of rearranging/grouping patches to make them most suited for submission, but if the

On 01/01/14 18:46, Ilia Mirkin wrote: > On Wed, Jan 1, 2014 at 9:04 AM, Sid Boyce <sboyce at blueyonder.co.uk> wrote: >> On 01/01/14 00:55, Ilia Mirkin wrote: >>> On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce <sboyce at blueyonder.co.uk> >>> wrote: >>>> On 31/12/13 10:36, Ilia Mirkin wrote: >>>>> Having a dmesg would be nice. One thing

Any comments? On 08.06.23 16:03, Juergen Gross wrote: > This is a small series getting rid of paravirt patching by switching > completely to alternative patching for the same functionality. > > The basic idea is to add the capability to switch from indirect to > direct calls via a special alternative patching option. > > This removes _some_ of the paravirt macro maze, but