search for: l341

OK, that works - looks like a documentation bug? (Also very confusing!) Should I report it on the page at https://wiki.asterisk.org/wiki/display/AST/Asterisk+17+AGICommand_get+full+variable or on the main tracker? Many thanks - couldn't figure out what was wrong! On Fri, 27 Dec 2019 at 19:36, Sean Bright <sean.bright at gmail.com> wrote: > On 12/27/2019 2:24 PM, Jonathan H wrote:

...ms ugly and requires a directory scan. I prefer (1), as administrators are still very likely to get it accidentally wrong, especially when setting up tinc in automated deployments. Thank you! Niklas [1] https://github.com/gsliepen/tinc/blob/5c344f297682cf11793407fca4547968aee22d95/src/net_setup.c#L341 [2] https://github.com/gsliepen/tinc/blob/1.1/src/net_setup.c#L389

Hello, I would like to ask what to pay attention to, when someone wants to set up multiple PuppetDB instances (and point them to the same DB), and put them behind a proxy/load balancer, as mentioned in the documentation<http://docs.puppetlabs.com/puppetdb/1/scaling_recommendations.html#bottleneck-single-point-of-failure> . Can this cause some concurrency issues with the message queues?

...some MIPS configs, and about to be > removed. It is implemented by the generic DMA mapping layer [1], which is used by a number of architectures including ARM64 and supposed to be used by new architectures going forward. [1] https://elixir.bootlin.com/linux/v5.9-rc1/source/kernel/dma/mapping.c#L341 When removing features from generic kernel code, I'd suggest first providing viable alternatives for its users, rather than killing the users altogether. Given the above, I'm afraid I have to NAK this. Best regards, Tomasz > > Signed-off-by: Christoph Hellwig <hch at lst.de>...

...aranteeing to the platform that you have all the correct and necessary sync points for this memory in the driver should it choose to return non-consistent memory." $ git grep dma_cache_sync drivers/media $ Robin. > [1] https://elixir.bootlin.com/linux/v5.9-rc1/source/kernel/dma/mapping.c#L341 > > When removing features from generic kernel code, I'd suggest first > providing viable alternatives for its users, rather than killing the > users altogether. > > Given the above, I'm afraid I have to NAK this. > > Best regards, > Tomasz > >> >&...

...of it. [1] https://elixir.bootlin.com/linux/v5.9-rc1/source/drivers/media/common/videobuf2/videobuf2-dma-contig.c#L98 [2] https://patchwork.kernel.org/comment/23312203/ Best regards, Tomasz > > Robin. > > > [1] https://elixir.bootlin.com/linux/v5.9-rc1/source/kernel/dma/mapping.c#L341 > > > > When removing features from generic kernel code, I'd suggest first > > providing viable alternatives for its users, rather than killing the > > users altogether. > > > > Given the above, I'm afraid I have to NAK this. > > > > Best rega...

Hi all, this series replaced the DMA_ATTR_NON_CONSISTENT flag to dma_alloc_attrs with a separate new dma_alloc_pages API, which is available on all platforms. In addition to cleaning up the convoluted code path, this ensures that other drivers that have asked for better support for non-coherent DMA to pages with incurring bounce buffering over can finally be properly supported. I'm still a