search for: reinstated

...athd: 3600144f00000000000005a2769c70001: remaining active paths: 3 Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: sde - directio checker reports path is up Dec 18 12:46:42 lemans kernel: device-mapper: multipath: Reinstating path 8:64. Dec 18 12:46:42 lemans multipathd: 8:64: reinstated Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: remaining active paths: 4 Dec 18 12:46:42 lemans multipathd: 3600144f00000000000005a2769c70001: sdk - directio checker reports path is up Dec 18 12:46:42 lemans kernel: device-mapper: multipath: Reinstating path 8:160. Dec 18 12:...

Signed-off-by: Roy Spliet <nouveau at spliet.org> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c | 59 +++++++++++++++++------ 1 file changed, 43 insertions(+), 16 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c b/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c index 62359c2..a469719 100644 --- a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c +++

On Wed, Jul 22, 2020 at 12:58:07PM -0500, Eric Blake wrote: [...] This is fine, but there is a minor thing: > docs/nbdkit-protocol.pod | 2 +- In the original patch I removed this hunk from nbdkit-protocol.pod: @@ -5,7 +5,7 @@ nbdkit - which parts of the NBD protocol nbdkit supports =head1 SYNOPSIS nbdkit [-n|--newstyle] [--mask-handshake MASK] [--no-sr] [-o|--oldstyle] -

Hi Jean-Marc, I'd like to lobby to put CELT_SET_SIGNALLING_REQUEST back into the public area. In our case the frame sizes are constant and we're not trying to be inter-operable with anyone else, so the in-band signaling byte is just wasted bandwidth. I know I could just modify the default value for "signalling" in the source code, but I'm trying to avoid doing that as

This disappeared when I removed the special case for ''.'' in btrfs_lookup() Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> --- super.c | 34 +++++++++++++++++++--------------- 1 files changed, 19 insertions(+), 15 deletions(-) diff --git a/super.c b/super.c index 55f4d00..f7b3eac 100644 --- a/super.c +++ b/super.c @@ -451,21 +451,25 @@ static int

It looks like for a while now (5 years) some code that was meant to do smart things in Mutex.cpp hasn't been doing such smart things: https://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Mutex.cpp?r1=29287&r2=29932&diff_format=h I don't know if this change was even deliberate since it came in with another change & the description doesn't mention it. Should we do

On Fri, Jan 13, 2012 at 10:24 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 13, 2012, at 4:43 PM, David Blaikie wrote: > >> It looks like for a while now (5 years) some code that was meant to do >> smart things in Mutex.cpp hasn't been doing such smart things: >> >>

On Jan 13, 2012, at 4:43 PM, David Blaikie wrote: > It looks like for a while now (5 years) some code that was meant to do > smart things in Mutex.cpp hasn't been doing such smart things: > > https://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Mutex.cpp?r1=29287&r2=29932&diff_format=h > > I don't know if this change was even deliberate since it came in

Full_Name: alex galanos Version: 2.10.0 OS: windows vista Submission from: (NULL) (86.11.78.110) I respectfully request that the chm help support for windows, which was very convenient, be reinstated...couldn't an online poll have been conducted to gauge the support of this format by window's users?

Hi 4.1.11 no longer includes the idmap_ad module in a default ./configure. This has caught out at least two list users recently. We think it is important enough to reinstate as default. Anyone with us? Especially those whose task it will be to have to tell users via the list of the change. . . Cheers, Steve

While we are unlikely to change our decision that -e should not control our response to NBD_OPT_LIST (because we intend to add a new callback .extents_list for that), it turns out that it is a lot easier to write: nbdkit -U - -e foo info --run 'nbdsh -u "$uri" -c "print(h.pread(3, 0))"' than it is to write the equivalent: nbdkit -U - info --run 'nbdsh -u

...ersonal, not corporate copyright attached. There were a couple of good reasons for this in the past, one of which was that we preferred GPL enforcement decisions to be made by individuals, not by corporations. Under GPLv2, a license violator loses all rights under the license and these have to be reinstated by the copyright holders, which made controlling who those copyright holders were very important. People are usually much more reasonable than corporations :-). With the move to GPLv3, this is much less important than it once was. The GPLv3, unlike GPLv2, allows an automatic reinstatement of right...

> On May 3, 2019, at 6:25 PM, Nadav Amit <namit at vmware.com> wrote: > >> On Apr 25, 2019, at 4:54 AM, Nadav Amit <namit at vmware.com> wrote: >> >> VMware balloon enhancements: adding support for memory compaction, >> memory shrinker (to prevent OOM) and splitting of refused pages to >> prevent recurring inflations. >> >> Patches

> On May 3, 2019, at 6:25 PM, Nadav Amit <namit at vmware.com> wrote: > >> On Apr 25, 2019, at 4:54 AM, Nadav Amit <namit at vmware.com> wrote: >> >> VMware balloon enhancements: adding support for memory compaction, >> memory shrinker (to prevent OOM) and splitting of refused pages to >> prevent recurring inflations. >> >> Patches

> On Apr 3, 2020, at 11:06 AM, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > >> >> >> Is it worth it? I think it is. But I am not sure I see the whole picture - >> are there low-memory systems that need to run LLVM on? >> >> I am not sure what needs to be done to approve such a fundamental change; >> especially when we

Hi all, The AsmPrinter class supports functions like EmitInt8, EmitInt16, and EmitInt32 for writing a 1/2/4 byte directive to the assembly. Each of these calls the MCStreamer::EmitIntValue method with the corresponding size. For some reason, there is no EmitInt64, and I was wondering if there was a fundamental reason why? The EmitIntValue function appears to support 8-byte inputs. I dug into

Ok, I give up. I tried, really hard, before asking but I must be the most stupid shorewall user on the planet :( My laptop runs a single eth0 interface and knows Net and Firewall as zones and the default "inbound" policies are Net->Any DROP and >ny->Any REJECT. Now at home I have my trusted 192.168.174.240/29 subnet which hosts my very trusted 192.168.174.242 host and I

...checked for other reports on this and can't find anything. It seems that the .Random.seed isn't updated properly after using rm(.Random.seed). Mu understanding from the help file indicates that a new 'random' seed will be generated. It appears that sometimes the old one is just reinstated. I removed my .RData file and the problem remains. It seems to happen when calls are made in succession to the same 'random generation type' function; but appears to work when different calls are made in succession. An example is given below. I was using the sample command when I found...

>I'll see if I can find some time this weekend to fix the elrepo package > and get it reinstated into the repository. >Phil Hi Phil, Thanks for the reply. Your correct this is OLD hardware. Everything was working with 7.5 thought I was good to go so to speak ... So When I was starting now to migrate OLD boxes from CentOS 6 to 7.6 it wasnt working. I can look at going "back" to...

Is there a trick to listing available providers? I can''t find it.