Occurences of swearing in the Linux kernel source code over time

Most uses of 'retard' are in variable names like B43legacy_OFDMTAB_ADVRETARD but we also have

That explains the sudden drop, with legacy code being removed

Either they have paragraphs of oddly specific insults or banana pi is becoming popular.

it relates to damnation and is basically short for 'i sentence you to eternal damnation/hell'

It lost all of its flare when being condemned to hell became a casual thing (eg. 'go to hell')

It'll never stop being funny to me how in the US it'a apparently considered pretty bad and even gets censored while here in germany it's one of those child friendly swears that you expect kindergarten kids to say.

And most of those cases are of course using the word sarcastically

::: spoiler collapsed list of them The next function to implement is called, amazingly, next(); its job is to move the iterator forward to the next position in the sequence.

if (lc->sync == NOSYNC)
	for (i = lc->header.nr_regions; i < lc->region_count; i++)
		/* FIXME: amazingly inefficient */
		log_set_bit(lc, lc->clean_bits, i);
else
	for (i = lc->header.nr_regions; i < lc->region_count; i++)
		/* FIXME: amazingly inefficient */
		log_clear_bit(lc, lc->clean_bits, i);

/*
 * Amazingly, if ehv_bc_tty_open() returns an error code, the tty layer will
 * still call this function to close the tty device.  So we can't assume that
 * the tty port has been initialized.
 */

 *   this header was blatantly ripped from netfilter_ipv4.h
 *   it's amazing what adding a bunch of 6s can do =8^)

/*
 * I studied different documents and many live PROMs both from 2.30
 * family and 3.xx versions. I came to the amazing conclusion: there is
 * absolutely no way to route interrupts in IIep systems relying on
 * information which PROM presents. We must hardcode interrupt routing
 * schematics. And this actually sucks.   -- zaitcev 1999/05/12

 * corresponding ABS_X and ABS_Y events. This turns the Twiddler into a game
 * controller with amazing 18 buttons :-)

 * In an amazing feat of design, the Enhanced Features Register (EFR)
 * shares the address of the Interrupt Identification Register (IIR).
 * Access to EFR is switched on by writing a magic value (0xbf) to the
 * Line Control Register (LCR). Any interrupt firing during this time will
 * see the EFR where it expects the IIR to be, leading to
 * "Unexpected interrupt" messages.

 * Thanks BUGabundo and Malmostoso for your amazing help!

:::

Did you just enter your password on here?

Would that be more or less, do you think?

I don't see a sharp drop as a sign of corporate oversight at all.

Stuff may be tackled en-batch. Or individuals can care. Or it can be an organic team decision or effort.