search for: 667,12

...uld be removed as well. > > diff --git a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > index 55e1756..bf78ce1 100644 > --- a/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > +++ b/lib/CodeGen/TargetLoweringObjectFileImpl.cpp > @@ -667,12 +667,6 @@ > TargetLoweringObjectFileMachO::getSectionForConstant(SectionKind Kind, > if (Kind.isDataRel() || Kind.isReadOnlyWithRel()) > return ConstDataSection; > > - if (Kind.isMergeableConst4()) > - return FourByteConstantSection; > - if (Kind.isMergeableCons...

In the mandriva rpm of rsync, we apply for our rpm the acl patch in the patches directory. I am trying to update our rpm to rsync 2.6.6 but one of the test failed with this patch. It seems to be a minor problem, but can you have a look ? Thanks by advance. Following the message (a bit long): ----- itemize log follows Testing for symlinks using 'test -h' +

...AX; } + +static inline bool is_swiotlb_active(void) +{ + return false; +} #endif /* CONFIG_SWIOTLB */ extern void swiotlb_print_info(void); diff --git a/kernel/dma/swiotlb.c b/kernel/dma/swiotlb.c index 9cb21259cb0b..c873f9cc2146 100644 --- a/kernel/dma/swiotlb.c +++ b/kernel/dma/swiotlb.c @@ -667,3 +667,12 @@ size_t swiotlb_max_mapping_size(struct device *dev) { return ((size_t)1 << IO_TLB_SHIFT) * IO_TLB_SEGSIZE; } + +bool is_swiotlb_active(void) +{ + /* + * When SWIOTLB is initialized, even if io_tlb_start points to physical + * address zero, io_tlb_end surely doesn't. +...

On Aug 25, 2014, at 8:26 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > On 21 August 2014 19:32, Akira Hatanaka <ahatanak at gmail.com> wrote: >> Is there a way to distinguish between GlobalValues that are user-defined and >> those that are compiler-defined? I am looking for a function that I can use >> to tell if a GlobalValue is user-defined ,

Hi, here is the next version of this patch-set. Previous versions can be found here: V1: https://lore.kernel.org/lkml/20190110134433.15672-1-joro at 8bytes.org/ V2: https://lore.kernel.org/lkml/20190115132257.6426-1-joro at 8bytes.org/ V3: https://lore.kernel.org/lkml/20190123163049.24863-1-joro at 8bytes.org/ V4: https://lore.kernel.org/lkml/20190129084342.26030-1-joro at 8bytes.org/

...fmt cmdline.size; g#add_drive ~readonly:false ~format:fmt fn; (* Helper drive for elements and binaries. *) g#add_drive_scratch (unit_GB 5); - (match drive with + (match cmdline.drive with | None -> g#add_drive_scratch (unit_GB 5) | Some drive -> @@ -667,12 +673,12 @@ let main () = g#mount "/dev/sdb" "/"; copy_in g auxtmpdir "/"; - copy_in g basepath "/lib"; + copy_in g cmdline.basepath "/lib"; g#umount "/"; (* Prepare the /aux/perm partition. *) let driv...

...ry: } if (call_ast) { - mlog(0, "calling unlockast(%p, %d)\n", data, lksb->status); + mlog(0, "calling unlockast(%p, %d)\n", data, status); if (is_master) { /* it is possible that there is one last bast * pending. make sure it is flushed, then @@ -677,9 +667,12 @@ retry: wait_event(dlm->ast_wq, dlm_lock_basts_flushed(dlm, lock)); } - (*unlockast)(data, lksb->status); + (*unlockast)(data, status); } + if (status == DLM_CANCELGRANT) + status = DLM_NORMAL; + if (status == DLM_NORMAL) { mlog(0, "kicking the thread\n&q...

From: Anand <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2)

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

Since the vTPM implementations are being incorproated into Xen and possibly upstream Linux, I would like to see if this protocol change could be added before we have significant legacy implementations. If not, I still think it would be useful as either a v2 or negotiated protocol change. The current vTPM protocol is a copy of the network protocol. This was likely done for ease of implementation,