Messages in this thread | | | Date | Fri, 11 Mar 2016 00:48:15 +0900 | From | Sergey Senozhatsky <> | Subject | Re: [RFC][PATCH v2 1/2] printk: Make printk() completely async |
| |
On (03/10/16 10:27), Jan Kara wrote: [..] > So I think this should definitely stay as a separate patch since it > possibly changes user visible behavior and sometimes blocking may be > actually desirable for userspace. I don't have that strong opinion whether > it should be in a separate patch set or part of this one. Maybe a separate > patch set would be somewhat better so that we first hash out possible issues > with async printk and once that's settled we start messing more with the > code changing the behavior of console_unlock() as well.
agree, thanks. I'll split the series and submit console_unlock() rework separately.
-ss
| |