similar to: PROPOSAL: Extend inline asm syntax with size spec

From: Geert Uytterhoeven > Sent: 24 February 2020 12:54 > To: Krzysztof Kozlowski <krzk at kernel.org> ... > > > > diff --git a/drivers/net/wireless/ath/ath5k/ahb.c b/drivers/net/wireless/ath/ath5k/ahb.c > > > > index 2c9cec8b53d9..8bd01df369fb 100644 > > > > --- a/drivers/net/wireless/ath/ath5k/ahb.c > > > > +++

Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales) Please consider the environment and don't print this e-mail unless you really need to -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20180713/b117ff94/attachment.html>

- Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales) Please consider the environment and don't print this e-mail unless you really need to

Hello all, I have,say 4 R objects... bar1, bar2, bar3, bar4.. that I'd like to include in an R package "foobar". The desired functionality would be: > library(foobar) > data(foo) > ls() [1] "bar1" "bar2" "bar3" "bar4" I've tried the following two approaches: 1) I created the file 'datalist' under pre-build directory

Hi there, RFC 5258 (IMAP4 LIST command extensions) defines a ?RECURSIVEMATCH? selection option which ?forces the server to return information about parent mailboxes that don't match other selection options, but have some submailboxes that do.? (Section 3.5 makes the requirement even clearer.) However that's not what Dovecot 2.3.7 does. AFAICT no LIST response is returned for mailboxes

Hi Geert, Le 08/01/2020 ? 09:43, Geert Uytterhoeven a ?crit?: > Hi Christophe, > > On Wed, Jan 8, 2020 at 9:35 AM Christophe Leroy <christophe.leroy at c-s.fr> wrote: >> Le 08/01/2020 ? 09:18, Krzysztof Kozlowski a ?crit : >>> On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: >>>> On Wed, Jan 8, 2020 at 9:07 AM Geert

This is an obscure R/S incompatibility but it is tripping up some code for us in the lme library. If you specify the contrasts argument in a call to model.matrix, that seems to take precedence over the interpretation of the formula. In S if the formula contains a "- 1", that will cause the contrasts to be suppressed. S> foo <- data.frame(bar = factor(rep(1:3, rep(2,3)))) S>

Hello, I want to have an operation foo with variable number of operands, and I am trying to achieve it using multiple operations. Let's say I want to have [FOO r1, r2], I am constructing the DAG as follows : consumeArg(r1) -> consumeArg(r2) -> FOO -> arg(r1) -> arg(r2) Note that the arrows are all "Chain"s. I need to have consumeArg(r1) because, I don't want the

Hello Mehdi Amini, Sorry for slow progress this week but it was due to interesting mistake of mine. I had build llvm with ipra enable by default and that build files were on my path ! Due to that next time I tried to build llvm it was terribly slow (almost 1 hour for 10% build ). I spend to much time on fixing this by playing around with environment variables, cmake options etc. But I think this

Dear List, I need a barplot with vertical bars. Each bar should have a label. The problem is, that the labels are too long, so they overlap, or only every seccond label is displayed in the output. Here is a little syntax: dd <- c(100,110,90,105,95) barplot(dd,names.arg=c('Conduct Disorders','Attention Deficit', 'Eating Disorders',

As mentioned in another thread, I notice that the params used to control symlinks feel a bit inefficient and inelegant, and quite limited. I think there might be a good opportunity to simplify and also make their management in Samba more powerful and adaptable to use-cases. I'm guessing this list is a good enough starting point to propose a smb.conf param change to this area and see what

On Sun, Jun 5, 2016 at 8:56 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Jun 4, 2016, at 7:56 PM, vivek pandya <vivekvpandya at gmail.com> wrote: > > > > Hello Mehdi Amini, > > > > Sorry for slow progress this week but it was due to interesting mistake > of mine. I had build llvm with ipra enable by default and that build files >

On Sun, Jun 5, 2016 at 9:15 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Jun 4, 2016, at 8:32 PM, vivek pandya <vivekvpandya at gmail.com> wrote: > > > > On Sun, Jun 5, 2016 at 8:56 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> > On Jun 4, 2016, at 7:56 PM, vivek pandya <vivekvpandya at gmail.com> >> wrote:

Hello, for some time now I wonder about the way the known_hosts file contains the server keys. Let's look at a part of my known_hosts file: shell.sf.net,66.35.250.208 ssh-dss AAAAB3NzaC1kc3MAAACBA... shell.sourceforge.net ssh-dss AAAAB3NzaC1kc3MAAACBA... As you can see, there are two entries, which describe the same host. When the file is empty and I do each connect after another, I

From: Jon Derrick <jonathan.derrick at intel.com> [ Upstream commit f10b83de1fd49216a4c657816f48001437e4bdd5 ] If the BAR is zero size, it indicates it was never successfully mapped. Ensure that the BAR is valid during initialization before attempting to use it. Signed-off-by: Jon Derrick <jonathan.derrick at intel.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com>

From: Jon Derrick <jonathan.derrick at intel.com> [ Upstream commit f10b83de1fd49216a4c657816f48001437e4bdd5 ] If the BAR is zero size, it indicates it was never successfully mapped. Ensure that the BAR is valid during initialization before attempting to use it. Signed-off-by: Jon Derrick <jonathan.derrick at intel.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com>

From: Jon Derrick <jonathan.derrick at intel.com> [ Upstream commit f10b83de1fd49216a4c657816f48001437e4bdd5 ] If the BAR is zero size, it indicates it was never successfully mapped. Ensure that the BAR is valid during initialization before attempting to use it. Signed-off-by: Jon Derrick <jonathan.derrick at intel.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com>

Yes, the hairy-edges of undefined behaviour - UB is UB. It does mean that given: __attribute__((noinline)) int foo(int a, int b) { return a + b; } int bar1(int x) { return foo(x, INT_MIN); } int bar2(int x) { return x + INT_MIN; } 'bar1' and 'bar2' have different outcomes. However, I think that the new optimisation is neat and valid and I am not suggesting that it should

I suspect the standard optimisation - breaking up the rsync into smaller batches - is not going to work for us. This is our situation: We rsync two directories in /spool to a backup. They are large: almost 2mil files in the first dir, with about 4mil hard links in the second one linking to them. The files don't change much; a few thousand added daily, and with about 3 hard links created for

On Thu, Feb 20, 2020 at 10:48:33AM +0100, Jiri Slaby wrote: > On 19. 02. 20, 18:50, Krzysztof Kozlowski wrote: > > The ioreadX() helpers have inconsistent interface. On some architectures > > void *__iomem address argument is a pointer to const, on some not. > > > > Implementations of ioreadX() do not modify the memory under the address > > so they can be