From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753969AbcAHBC2 (ORCPT ); Thu, 7 Jan 2016 20:02:28 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:40482 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753912AbcAHBC1 (ORCPT ); Thu, 7 Jan 2016 20:02:27 -0500 Date: Thu, 7 Jan 2016 17:02:00 -0800 From: Greg Kroah-Hartman To: "Winkler, Tomas" Cc: "Usyskin, Alexander" , "linux-kernel@vger.kernel.org" Subject: Re: [char-misc-next RESEND 0/6] mei updates Message-ID: <20160108010200.GB4503@kroah.com> References: <1452170799-16960-1-git-send-email-tomas.winkler@intel.com> <20160107173109.GB29783@kroah.com> <5B8DA87D05A7694D9FA63FD143655C1B5411EB10@hasmsx108.ger.corp.intel.com> <20160107230818.GA12097@kroah.com> <5B8DA87D05A7694D9FA63FD143655C1B5411EB55@hasmsx108.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B5411EB55@hasmsx108.ger.corp.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 07, 2016 at 11:32:20PM +0000, Winkler, Tomas wrote: > > > > > On Thu, Jan 07, 2016 at 10:56:34PM +0000, Winkler, Tomas wrote: > > > > > > > > > > On Thu, Jan 07, 2016 at 02:46:33PM +0200, Tomas Winkler wrote: > > > > > I've sent those patches ~ two months ago but were probably dropped from > > > > > the queue so resending them again. > > > > > > > > sorry, they are still in there, it's been a busy few months, I'll get to > > > > these for the next release, it's too late for this one, my fault. > > > > > > Can you be specific what is next release, the merging window is still not open... > > > > The "merge window" is for subsystem maintainers to merge to Linus, I > > have to have my tree "closed" for a week before that for linux-next to > > settle down. It's been this way for a very long time. > > Understood, I've just paid attention that the parport patches was > applied last few days so I've also tried my luck Anyhow please > reconsider ' mei: fix fasync return value on error' which was > originally indented for 4.4-rc5 and should go to the stable. the parport ones were tiny code style issues. I'll go look at this fasync patch now... thanks, greg k-h