rtc-pcf85063: break comments at 80 chars

linux_kernel_modules/rtc-pcf85063/rtc-pcf85063.c

@@ -7,13 +7,12 @@
  *
  * based on the other drivers in this same directory.
  *
- * Sierra Wireless Inc. - Added on functionality to allow
- * control of the square-wave clkout frequencies via sysfs entries.
- * Note, this was developed in the context of the MangOH Yellow board
- * which has the square-wave clkout pin connected to a buzzer. Thus,
- * one can drive the buzzer for the allowable frequencies, note
- * humans can only recognize 20 - 20KHz (some of us, like your author
- * even less).
+ * Sierra Wireless Inc. - Added on functionality to allow control of the
+ * square-wave clkout frequencies via sysfs entries. Note, this was developed in
+ * the context of the MangOH Yellow board which has the square-wave clkout pin
+ * connected to a buzzer. Thus, one can drive the buzzer for the allowable
+ * frequencies, note humans can only recognize 20 - 20KHz (some of us, like your
+ * author even less).
  *
  * This program is free software; you can redistribute it and/or modify
  * it under the terms of the GNU General Public License version 2 as
@@ -58,13 +57,12 @@ static const int clkout_freq_table[NUM_FREQUENCIES][2] = {
 static struct i2c_driver pcf85063_driver;
 
 /*
- * We need to define a mutex here because the rtc_sync module in MangOH
- * can call into rtc_set_time while sysfs is changing the square-wave
- * output frequencies. Ditto for rtc_read_time from rtc_sync.
- * We wouldn't need the mutex if a workQ handler was defined for this device
- * but then the rtc_sync module would not be generic. Just be aware that
- * any rtc chip that allows rtc_sync to call into it needs a mutex if any
- * other threaded access will concurrently exist.
+ * We need to define a mutex here because the rtc_sync module in MangOH can call
+ * into rtc_set_time while sysfs is changing the square-wave output frequencies.
+ * Ditto for rtc_read_time from rtc_sync. We wouldn't need the mutex if a workQ
+ * handler was defined for this device but then the rtc_sync module would not be
+ * generic. Just be aware that any rtc chip that allows rtc_sync to call into it
+ * needs a mutex if any other threaded access will concurrently exist.
  */
 static DEFINE_MUTEX(pcf85063_rtc_mutex);