search for: hugging

On Fri, 30 Nov 2018 20:39:01 +0000 Abuse <abuse at 2.abuse.bgcomp.co.uk> wrote: > On Friday, 30 November 2018 20:35:07 GMT David Miller wrote: > > From: Jens Axboe <axboe at kernel.dk> > > Date: Fri, 30 Nov 2018 13:12:26 -0700 > > > > > On 11/30/18 12:56 PM, Davidlohr Bueso wrote: > > >> On Fri, 30 Nov 2018, Kees Cook wrote: > >

On Friday, 30 November 2018 20:35:07 GMT David Miller wrote: > From: Jens Axboe <axboe at kernel.dk> > Date: Fri, 30 Nov 2018 13:12:26 -0700 > > > On 11/30/18 12:56 PM, Davidlohr Bueso wrote: > >> On Fri, 30 Nov 2018, Kees Cook wrote: > >> > >>> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen > >>> <jarkko.sakkinen at

In order to comply with the CoC, replace **** with a hug. Jarkko Sakkinen (15): MIPS: replace **** with a hug Documentation: replace **** with a hug drm/nouveau: replace **** with a hug m68k: replace **** with a hug parisc: replace **** with a hug cpufreq: replace **** with a hug ide: replace **** with a hug media: replace **** with a hug mtd: replace **** with a hug

On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com> wrote: > > In order to comply with the CoC, replace **** with a hug. Heh. I support the replacement of the stronger language, but I find "hug", "hugged", and "hugging" to be very weird replacements. Can we bikeshed this to "heck", "hecked", and "hecking" (or "heckin" to follow true Doggo meme style). "This API is hugged" doesn't make any sense to me. "This API is hecked" is better, or at least...

...30, 2018 at 11:27 AM Jarkko Sakkinen > <jarkko.sakkinen at linux.intel.com> wrote: >> >> In order to comply with the CoC, replace **** with a hug. > > Heh. I support the replacement of the stronger language, but I find > "hug", "hugged", and "hugging" to be very weird replacements. Can we > bikeshed this to "heck", "hecked", and "hecking" (or "heckin" to > follow true Doggo meme style). > > "This API is hugged" doesn't make any sense to me. "This API is > hecked&quo...

...v 30, 2018 at 11:27 AM Jarkko Sakkinen > <jarkko.sakkinen at linux.intel.com> wrote: >> >> In order to comply with the CoC, replace **** with a hug. > > Heh. I support the replacement of the stronger language, but I find > "hug", "hugged", and "hugging" to be very weird replacements. Can we > bikeshed this to "heck", "hecked", and "hecking" (or "heckin" to > follow true Doggo meme style). > > "This API is hugged" doesn't make any sense to me. "This API is > hecked&quot...

On Fri, 30 Nov 2018, Kees Cook wrote: >On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen ><jarkko.sakkinen at linux.intel.com> wrote: >> >> In order to comply with the CoC, replace **** with a hug. I hope this is some kind of joke. How would anyone get offended by reading technical comments? This is all beyond me... Thanks, Davidlohr

...restrict(struct nvbios_init *init) > { > /* This appears to be the behaviour of the VBIOS parser, and *is* > * important to cache the NV_PEXTDEV_BOOT0 on later chipsets to > - * avoid fucking up the memory controller (somehow) by reading it > + * avoid hugging up the memory controller (somehow) by reading it > * on every INIT_RAM_RESTRICT_ZM_GROUP opcode. > * > * Preserving the non-caching behaviour on earlier chipsets just > diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc b/drivers/gpu/drm/nouve...

thanks But does not show the difference between versions. hug   Citando Markus Dellermann via samba <samba at lists.samba.org>: > Am Donnerstag, 8. Dezember 2016, 13:39:21 CET schrieb Edson via samba: >> Difference of versions: >> >> Samba 4.5.2 >> >> Samba 4.3.12 >> >> Samba 4.4.7 >> >> Sernet >> >> hug!!! > >

Am 01.12.2018 um 09:12 schrieb Jens Axboe: > On 11/30/18 12:56 PM, Davidlohr Bueso wrote: >> On Fri, 30 Nov 2018, Kees Cook wrote: >> >>> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen >>> <jarkko.sakkinen at linux.intel.com> wrote: >>>> >>>> In order to comply with the CoC, replace **** with a hug. >> >> I hope this is

.../subdev/bios/init.c @@ -446,7 +446,7 @@ init_ram_restrict(struct nvbios_init *init) { /* This appears to be the behaviour of the VBIOS parser, and *is* * important to cache the NV_PEXTDEV_BOOT0 on later chipsets to - * avoid fucking up the memory controller (somehow) by reading it + * avoid hugging up the memory controller (somehow) by reading it * on every INIT_RAM_RESTRICT_ZM_GROUP opcode. * * Preserving the non-caching behaviour on earlier chipsets just diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc b/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc inde...

...it *init) > > { > > /* This appears to be the behaviour of the VBIOS parser, and *is* > > * important to cache the NV_PEXTDEV_BOOT0 on later chipsets to > > - * avoid fucking up the memory controller (somehow) by reading it > > + * avoid hugging up the memory controller (somehow) by reading it > > * on every INIT_RAM_RESTRICT_ZM_GROUP opcode. > > * > > * Preserving the non-caching behaviour on earlier chipsets just > > diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc b/d...

...{ > > > /* This appears to be the behaviour of the VBIOS parser, and *is* > > > * important to cache the NV_PEXTDEV_BOOT0 on later chipsets to > > > - * avoid fucking up the memory controller (somehow) by reading it > > > + * avoid hugging up the memory controller (somehow) by reading it > > > * on every INIT_RAM_RESTRICT_ZM_GROUP opcode. > > > * > > > * Preserving the non-caching behaviour on earlier chipsets just > > > diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pm...

On 11/30/18 12:56 PM, Davidlohr Bueso wrote: > On Fri, 30 Nov 2018, Kees Cook wrote: > >> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen >> <jarkko.sakkinen at linux.intel.com> wrote: >>> >>> In order to comply with the CoC, replace **** with a hug. > > I hope this is some kind of joke. How would anyone get offended by reading > technical

...arassing photography or recording, inappropriate physical contact, sexual imagery and unwelcome sexual advances or requests for sexual favors." Doesn't this fall into this category? Your argument is not that great because you could say that from any LKML discussion. If you don't like hugging, please propose something else :-) /Jarkko

Difference of versions: Samba 4.5.2 Samba 4.3.12 Samba 4.4.7 Sernet hug!!!

From: Jens Axboe <axboe at kernel.dk> Date: Fri, 30 Nov 2018 13:12:26 -0700 > On 11/30/18 12:56 PM, Davidlohr Bueso wrote: >> On Fri, 30 Nov 2018, Kees Cook wrote: >> >>> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen >>> <jarkko.sakkinen at linux.intel.com> wrote: >>>> >>>> In order to comply with the CoC, replace **** with

On Fri, Nov 30, 2018 at 12:35:07PM -0800, David Miller wrote: > From: Jens Axboe <axboe at kernel.dk> > Date: Fri, 30 Nov 2018 13:12:26 -0700 > > > On 11/30/18 12:56 PM, Davidlohr Bueso wrote: > >> On Fri, 30 Nov 2018, Kees Cook wrote: > >> > >>> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen > >>> <jarkko.sakkinen at

...ily abusive, offensive or degrading. Our most heavily censored medium is TV and "fuck" is now considered acceptable in certain contexts on most channels in the UK and EU. > Your argument is not that great because you could say that from any > LKML discussion. If you don't like hugging, please propose something > else > :-) The interpretation document also says this: ontributions submitted for the kernel should use appropriate language. Content that already exists predating the Code of Conduct will not be addressed now as a violation. So that definitely means th...

I need to import several ascii files in fixed format with two different record types. The data comes from European Labor Force Surveys, wich is a household survey. The first record type is for people over 16 years, and the second much sorter is for people aged 15 or less (this record has a filler with several blanks to get the same record length). The files tipically have 160000 records, with 176