From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: [char-misc-next RESEND 0/6] mei updates
Date: Wed, 27 Jan 2016 21:22:17 +0000 [thread overview]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B54157B98@hasmsx109.ger.corp.intel.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B5411EB55@hasmsx108.ger.corp.intel.com>
>
>
> >
> > 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
next prev parent reply other threads:[~2016-01-27 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 12:46 [char-misc-next RESEND 0/6] mei updates Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 1/6 RESEND] mei: bus: remove redundant uuid string in debug messages Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 2/6 RESEND] mei: trace pci configuration space io Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 3/6 RESEND] mei: prevent queuing new flow control credit Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 4/6 RESEND] mei: always copy the read buffer if data is ready Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 5/6 RESEND] mei: fix fasync return value on error Tomas Winkler
2016-01-07 12:46 ` [char-misc-next 6/6 RESEND] mei: drop nfc leftovers from the mei driver Tomas Winkler
2016-01-07 17:31 ` [char-misc-next RESEND 0/6] mei updates Greg Kroah-Hartman
2016-01-07 22:56 ` Winkler, Tomas
2016-01-07 23:08 ` Greg Kroah-Hartman
2016-01-07 23:32 ` Winkler, Tomas
2016-01-08 1:02 ` Greg Kroah-Hartman
2016-01-09 4:59 ` Sudip Mukherjee
2016-01-09 5:10 ` Greg Kroah-Hartman
2016-01-09 5:27 ` Sudip Mukherjee
2016-01-27 21:22 ` Winkler, Tomas [this message]
2016-01-27 21:27 ` 'Greg Kroah-Hartman'
2016-01-27 21:33 ` Winkler, Tomas
2016-02-07 6:09 ` Greg Kroah-Hartman
2016-02-07 9:17 ` Winkler, Tomas
2016-02-07 17:33 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B8DA87D05A7694D9FA63FD143655C1B54157B98@hasmsx109.ger.corp.intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.