)]}'
{
  "commit": "79492689e40d4f4d3d8a7262781d56fb295b4b86",
  "tree": "f66255875725b87a986300735db7fe0212415695",
  "parents": [
    "23936cc0b5d89619c34c2dab11d8cf3d6f7ca028"
  ],
  "author": {
    "name": "Yinghai Lu",
    "email": "Yinghai.Lu@Sun.COM",
    "time": "Sun Jul 15 23:37:25 2007 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.linux-foundation.org",
    "time": "Mon Jul 16 09:05:34 2007 -0700"
  },
  "message": "serial: assert DTR for serial console devices\n\nSome RS-232 devices require DTR to be asserted before they can be used.  DTR\nis normally asserted in uart_startup() when the port is opened.  But we don\u0027t\nactually open serial console ports, so assert DTR when the port is added.\n\nBTW:\nearlyprintk and early_uart are hard coded to set DTR/RTS.\n\nrmk says\n\n  The only issue I can think of is the possibility for an attached modem to\n  auto-answer or maybe even auto-dial before the system is ready for it to do\n  so.  Might have an undesirable cost implication for some running with such a\n  setup.\n\n  Apart from that, I can\u0027t think of any other side effect of this specific\n  patch.\n\nSigned-off-by: Yinghai Lu \u003cyinghai.lu@sun.com\u003e\nAcked-by: Russell King \u003crmk@arm.linux.org.uk\u003e\nCc: Andi Kleen \u003cak@suse.de\u003e\nCc: Bjorn Helgaas \u003cbjorn.helgaas@hp.com\u003e\nCc: Gerd Hoffmann \u003ckraxel@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "326020f86f757e98ef6f148754cdb1e355ee75b3",
      "old_mode": 33188,
      "old_path": "drivers/serial/serial_core.c",
      "new_id": "9c57486c2e7fe20783b004dad25475b4cc805358",
      "new_mode": 33188,
      "new_path": "drivers/serial/serial_core.c"
    }
  ]
}
