{"push_id":948003064,"size":4,"distinct_size":4,"ref":"refs/heads/stable/10","head":"55146b62a12461f40c96f1aea09d60a020b63c22","before":"650a9addf1aa6411b6dfefe94fcf78fe0b856fe8","commits":[{"sha":"e24c3b20d06b07f1ab29cac41517fc3325c2d973","author":{"email":"57a33a5496950fec8433e4dd83347673459dcdfc@FreeBSD.org","name":"ian"},"message":"MFC r293830:\n\n  Fix the spelling of fueword* to eliminate compile warnings about mismatched\n  begin/end symbols when the warning level is turned up.","distinct":true,"url":"https://api.github.com/repos/freebsd/freebsd/commits/e24c3b20d06b07f1ab29cac41517fc3325c2d973"},{"sha":"d334c6626811b46e187e354b29cb278f40871783","author":{"email":"57a33a5496950fec8433e4dd83347673459dcdfc@FreeBSD.org","name":"ian"},"message":"MFC r294032:\n\n  Fix the handling of the \"PDC write transfer length\" erratum for at91.  The\n  problem affects revision 1xx hardware as well as later versions.  Also, the\n  recommended workaround is to set the PDC count register for a 12-byte\n  transfer when the actual size is less than that, but there is no need to\n  extend or zero-out the data buffer, because the blklen register contains\n  the real transfer size and only that many bytes will be transferred.\n\n  Also add a sysctl to turn debugging printfs on or off on the fly.","distinct":true,"url":"https://api.github.com/repos/freebsd/freebsd/commits/d334c6626811b46e187e354b29cb278f40871783"},{"sha":"495cfa3822731e7518c9829f6cc09dc1f92515b6","author":{"email":"57a33a5496950fec8433e4dd83347673459dcdfc@FreeBSD.org","name":"ian"},"message":"MFC r293105:\n\n  Eliminate code for walking through the early static env data.  This code\n  is called from a device attach routine, and thus cannot be called before\n  the cutover from static to dynamic kernel env.","distinct":true,"url":"https://api.github.com/repos/freebsd/freebsd/commits/495cfa3822731e7518c9829f6cc09dc1f92515b6"},{"sha":"55146b62a12461f40c96f1aea09d60a020b63c22","author":{"email":"57a33a5496950fec8433e4dd83347673459dcdfc@FreeBSD.org","name":"ian"},"message":"MFC r289477:\n\n  Fix a strange macro re-definition compile error.  If the VM_MAXUSER_ADDRESS\n  value is defined as a config option the definition is emitted into\n  opt_global.h which is force-included into everything.  In addition, the\n  symbol is emitted by the genassym mechanism, but that by its nature reduces\n  the value to a 0xnnnnnnnn number.  When compiling a .S file you end up\n  with two different definitions of the macro (they evaluate to the same\n  number, but the text is different, upsetting the compiler).","distinct":true,"url":"https://api.github.com/repos/freebsd/freebsd/commits/55146b62a12461f40c96f1aea09d60a020b63c22"}]}