similar to: 10) Don't get discouraged. Re-submit.

The previous patch renamed several files that are cross-referenced along the Kernel documentation. Adjust the links to point to the right places. Signed-off-by: Mauro Carvalho Chehab <mchehab at s-opensource.com> --- Documentation/00-INDEX | 54 +++++++++++----------- Documentation/ABI/README | 2 +-

The previous patch renamed several files that are cross-referenced along the Kernel documentation. Adjust the links to point to the right places. Signed-off-by: Mauro Carvalho Chehab <mchehab at s-opensource.com> --- Documentation/00-INDEX | 54 +++++++++++----------- Documentation/ABI/README | 2 +-

The previous patch renamed several files that are cross-referenced along the Kernel documentation. Adjust the links to point to the right places. Most of the work here was made via a perl script. Two files that got renamed (HOWTO and Changes) required manual work, as there's a high number of false positives. <script> #!/usr/bin/perl use File::Find; my $show_string; $show_string=shift

The previous patch renamed several files that are cross-referenced along the Kernel documentation. Adjust the links to point to the right places. Most of the work here was made via a perl script. Two files that got renamed (HOWTO and Changes) required manual work, as there's a high number of false positives. <script> #!/usr/bin/perl use File::Find; my $show_string; $show_string=shift

Hello all, I have just released SYSLINUX 3.62. This is almost identical to 3.62-pre16, with a small number of changes to the Makefiles and documentation. The focus of this release has largely been removing build-in limitations as much as possible. Quite a bit of work has gone into it. I'd like to specially thank my employer, rPath Inc.; I've spent a lot of time on this I wouldn't

> Please attach patches as attachments (and name the file > ".patch" just in case). Mail readers commonly munge them > (e.g. by removing trailing whitespace) if not, which prevents > the patch from applying. I hope that this is not off-topic, but why is this? I'm doing some amount of linux-driver kernel work, and there you are urged to insert your patch directly into

They can get bitten in the last two lines of this example, where the 'x' argument is not first: > d <- data.frame(C1=c(r1=11,r2=21,r3=31), C2=c(12,22,32)) > d[1,1:2] C1 C2 r1 11 12 > `[`(d,j=1:2,i=1) C1 C2 r1 11 12 Warning message: In `[.data.frame`(d, j = 1:2, i = 1) : named arguments other than 'drop' are discouraged > `[`(j=1:2,d,i=1) Error in (1:2)[d, i =

Well, the situation with `[.data.frame` (and [<-) is complicated by the fact that the data.frame-method is not a primitive, but the generic IS. I'm not sure about dispatch for primitive-generics, but I bet it's done on the first argument (as with S3). Which means `[`(j=1:2,d,i=1) has nothing to do with `[.data.frame`, as some internal code equivalent to something like `[.integer` is

After hearing all the rave about Half-Life/Counter-Strike on Wine I decided to take the plunge myself... after rpm -e the default OLD wine packages from my RH7.2 install I installed wine20011004 graciously provided by http://www.linux-easy.com/daily/ ... setup my ~/.wine/config and got VERY UPSET when Half-Life install would even work... barfing the folloowing message! :( [msowka@mainframe

tl;dr: Why are named arguments discouraged in `[.data.frame`, `[<-.data.frame` and `[[.data.frame`? (because this question is of the kind 'why is R designed like this?', I though R-devel would be more appropriate than R-help) ############################# Background: Now and then students presents there fancy functions like this:

Hi Joe, [auto build test WARNING on drm/drm-next] [also build test WARNING on next-20160318] [cannot apply to v4.5] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Joe-Perches/gpu-drm-Use-u64_to_user_pointer/20160319-012749 base: git://people.freedesktop.org/~airlied/linux.git drm-next config:

On Thu, 2018-06-07 at 10:26 -0700, Nick Desaulniers wrote: > I get the feeling that the use of __inline__ or __inline (vs inline) > in the kernel may be wrong and their use should be eradicated in the > follow up patch set, but it would be cool if others have additional > insight. __inline is easy and useful to remove as it's used in just a few files. But __inline__ is used in a

Linus, Rusty asked me to resolve any issues with virtio and lguest that surface, so here comes. Thanks! The following changes since commit 847f9c606cad121cebf984639e3eeee1c4db82f8: Linus Torvalds (1): Merge branch 'for-linus' of git://git.kernel.org/.../geert/linux-m68k are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git

Linus, Rusty asked me to resolve any issues with virtio and lguest that surface, so here comes. Thanks! The following changes since commit 847f9c606cad121cebf984639e3eeee1c4db82f8: Linus Torvalds (1): Merge branch 'for-linus' of git://git.kernel.org/.../geert/linux-m68k are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git

>> could it be implemented? If that's not possible, what's doing SysLinux > > Consider bios/mtools/syslinux Just what I needed, thanks! :-D I have not seen any reference to that on the wiki docs, maybe it would make sense to add a little note about it? And regarding to the extra modules (menu.c32 and so), I need to add them previously by hand, isn't it? Just to be sure...

Thanks Bill and Michael for taking the time to share your knowledge! As a further background to my question, here are two examples that I forgot to include in my original post (reminded by Michael's answer). I swapped the i and j arguments in `[.data.frame` and `[<-.data.frame`. With warnings, but else without (?) problem. Using Bill's data: `[.data.frame`(x = d, i = 1, j = 2) # [1]

Hi Some time ago I wrote this mailing list about some extra time that it takes for my system to boot and I don't know where it came from.I'm using a custom BIOS which loads at 1 second and now I've found out that it takes for the bootloader and OS an extra 1 second to load when keyboard is disconnected.I got from the BIOS engineer the following explanation and steps to take: In

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: > On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > As a result of backporting a bugfix, virtio_net started passing void * > > to page_address, assuming that it will get silently converted to struct > > page *. But this does not happen on architectures where page_address

--- On Thu, 5/31/12, Geert Stappers <stappers at stappers.nl> wrote: > > P.S. > > As usual, eagerly (and patiently) waiting for the HTTP > bits to start > > working properly! ;) :) > > How should I read that??.? Does it mean "I'm waiting to > get time to test" > or do you mean "tested, it doesn't work yet"??? > Anyway, please