Re: [char-misc-next RESEND 0/6] mei updates

[Sudip Mukherjee <sudipm.mukherjee@gmail.com>]

On Fri, Jan 08, 2016 at 09:10:11PM -0800, Greg Kroah-Hartman wrote:
> On Sat, Jan 09, 2016 at 10:29:52AM +0530, Sudip Mukherjee wrote:
> > 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@windriver.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. :)
> 
> Ah crap, I though I had picked up the needed tty/serial fixes, but I
> missed that one, thanks, will go get to it now...

Thanks.

> 
> Is there anything else that you happened to notice that I should get
> into 4.5-rc1 that I missed?

Nothing else from your side I guess, atleast not related to any build
failure that i monitor. There will be build failure related to some other
patches, one in drm and one in media. They are not yet in linux-next so
I don't have any idea if they will be included for rc1 or not.

regards
sudip