search for: overcauti

FWIW, I’d like for us to come to an agreement before the branch for LLVM 7.0 is cut. How do others feel about this? Am I wrong when I claim that shipping an ABI-unstable feature in the std:: namespace is a deviation from normal practice? Am I overcautious when I say it’s asking for trouble? Eric, I know you’re busy and may not have time to do the work so I’m totally willing to chime in, but I’d like to have your thoughts on my objection first. Cheers, Louis > On Jul 27, 2018, at 17:02, Louis Dionne via cfe-dev <cfe-dev at lists.llvm.org&...

....llvm.org> wrote: >> FWIW, I’d like for us to come to an agreement before the branch for LLVM 7.0 >> is cut. How do others feel about this? Am I wrong when I claim that shipping >> an ABI-unstable feature in the std:: namespace is a deviation from normal >> practice? Am I overcautious when I say it’s asking for trouble? >> >> Eric, I know you’re busy and may not have time to do the work so I’m totally >> willing to chime in, but I’d like to have your thoughts on my objection >> first. >> >> Cheers, >> Louis >> >> >&...

...ichael S. Tsirkin" <mst at redhat.com> writes: > Hi Rusty! > There are a bunch of (mostly virtio 1.0 related) fixes for virtio > that need to go into 4.0 I think. > virtio_blk: typo fix > virtio_blk: fix comment for virtio 1.0 OK, I've added these two. I tend to be overcautious after the merge window. > virtio_console: init work unconditionally > virtio_console: avoid config access from irq > virtio_balloon: set DRIVER_OK before using device > > seem ready? These are in my virtio-next tree already. > virtio_mmio: generation support > virt...

...ichael S. Tsirkin" <mst at redhat.com> writes: > Hi Rusty! > There are a bunch of (mostly virtio 1.0 related) fixes for virtio > that need to go into 4.0 I think. > virtio_blk: typo fix > virtio_blk: fix comment for virtio 1.0 OK, I've added these two. I tend to be overcautious after the merge window. > virtio_console: init work unconditionally > virtio_console: avoid config access from irq > virtio_balloon: set DRIVER_OK before using device > > seem ready? These are in my virtio-next tree already. > virtio_mmio: generation support > virt...

...come to an agreement before the branch for >> LLVM 7.0 >> >> is cut. How do others feel about this? Am I wrong when I claim that >> shipping >> >> an ABI-unstable feature in the std:: namespace is a deviation from >> normal >> >> practice? Am I overcautious when I say it’s asking for trouble? >> >> >> >> Eric, I know you’re busy and may not have time to do the work so I’m >> totally >> >> willing to chime in, but I’d like to have your thoughts on my objection >> >> first. >> >> >&...

Hi Rusty! There are a bunch of (mostly virtio 1.0 related) fixes for virtio that need to go into 4.0 I think. virtio_blk: typo fix virtio_blk: fix comment for virtio 1.0 virtio_console: init work unconditionally virtio_console: avoid config access from irq virtio_balloon: set DRIVER_OK before using device seem ready? virtio_mmio: generation support virtio_mmio: fix endian-ness for mmio

Hi Rusty! There are a bunch of (mostly virtio 1.0 related) fixes for virtio that need to go into 4.0 I think. virtio_blk: typo fix virtio_blk: fix comment for virtio 1.0 virtio_console: init work unconditionally virtio_console: avoid config access from irq virtio_balloon: set DRIVER_OK before using device seem ready? virtio_mmio: generation support virtio_mmio: fix endian-ness for mmio

...granted that the data in that extent is not lost. In order to implement it, we just write out all the dirty pages which are beyond the expected size of the file. This operation will spend lots of time if there are many dirty pages. It is also the only disadvantage of this patch. (Maybe I''m overcautious, we needn''t hold that data.) Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/inode.c | 159 +++++++++++++++++------------------------------------- 1 files changed, 49 insertions(+), 110 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index df6060f..9a...

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.15.tar.gz.sig Some small fixes and changes to v2.2.14. This release is mainly in the hope that it could still make it into the next Debian stable instead of v2.2.14 - mainly because of a couple of new assert crashes that started happening in v2.2.14 and should be fixed now. * Plugins can now print

Hi All, I recently committed <filesystem> to trunk. I wanted to bring attention to some quirks it currently has. First, it's been put in a separate library, libc++fs, for now. Users are responsible for linking the library when they use filesystem. Second, it should still not be considered ABI stable. Vendors should be aware of this before shipping it. Hopefully all the standard and