On 18/10/2018 11:57, Igor Mammedov wrote: > > I'm posting this first, so post_plug() won't confuse people and > won't introduce a new code that would depend on it or even worse > some plug handler would depend on plug() happening before reset. > This patch should prevent that from happening. (Error** concerns > are secondary here and I'll deal with it later on, hopefully > during 3.2 cycle) > > PS: > post_plug() is recurring idea which indicates that current plug() > is misplaced. (previous instance that's slipped in, was nvdimm's > 75b0713e1 which was removed later on by c7f8d0f3a5).
Ok, queued. Paolo
