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]
Date:	Sat, 9 Jan 2016 10:29:52 +0530
From:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	"Winkler, Tomas" <tomas.winkler@...el.com>,
	"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 05:02:00PM -0800, Greg Kroah-Hartman wrote:
> 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 for the parport. I didn't expect you will apply that at this
time.
Can you please also have a look at:
[PATCH] drivers/tty/serial: delete unused MODULE_DEVICE_TABLE from atmel_serial.c
by Paul Gortmaker <paul.gortmaker@...driver.com>

rc1 allmodconfig build will fail in some arch without this. But no hurries,
since it is a fix it can go for rc2 also. :)

regards
sudip

Powered by blists - more mailing lists