linux-kernel - RE: [char-misc-next RESEND 0/6] mei updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B54157B98@hasmsx109.ger.corp.intel.com>
Date:	Wed, 27 Jan 2016 21:22:17 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>
CC:	"Usyskin, Alexander" <alexander.usyskin@...el.com>,
	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: RE: [char-misc-next RESEND 0/6] mei updates

> 
> 
> >
> > 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.
> 
> >
> > > I have tons of patches it is just blocked by the watchdog removal from
> > > the core driver, which I've just reposted as well on top of this
> > > series.
> >
> > Sorry for the delay these past 2 months, should be caught up for the
> > next release cycle.  And your watchdog repost wouldn't have made it into
> > this release anyway :)
> 
> Okay, I would just ask you to do give some priority to review our patches after
> the merging window so I don't have to carry too long queue for months.

Hello Greg, 
After 4.5-rc1 was tagged, I would like to start sending  our patches for the char-misc-next branch 
I wonder if to resend the whole queue rebased or 4.5-rc1 or continuation of this series. 
 
Tomas
Thanks