mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [char-misc-next 0/3]  mei: driver cleanups
Date: Mon, 11 Nov 2013 15:14:42 +0000	[thread overview]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B1AF0929D@HASMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <20131111150212.GA16112@kroah.com>



> -----Original Message-----
> From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> Sent: Monday, November 11, 2013 17:02
> To: Winkler, Tomas
> Cc: arnd@arndb.de; linux-kernel@vger.kernel.org
> Subject: Re: [char-misc-next 0/3] mei: driver cleanups
> 
> On Mon, Nov 11, 2013 at 11:35:40AM +0000, Winkler, Tomas wrote:
> >
> >
> > >
> > > *** BLURB HERE ***
> > Oops, sorry for that.
> 
> So, any hint for what these are for?  I can't take patches until
> 3.13-rc1 is out, which will be a few weeks.  But then, which should this
> be for, 3.13 as these are regression fixes, or 3.14 as they are only
> "cleanups"?

No regressions here, I don't mind it will be in 3.14
I will mark fixes 3.13 properly (hopefully w/o BLURB)

Tomas


      reply	other threads:[~2013-11-11 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 11:26 Tomas Winkler
2013-11-11 11:26 ` [char-misc-next 1/3] mei: remove flash_work_queue Tomas Winkler
2013-11-11 11:26 ` [char-misc-next 2/3] mei: drop redundant list_del_init Tomas Winkler
2013-11-11 11:26 ` [char-misc-next 3/3] mei: cleanup mei_irq_read_handler Tomas Winkler
2013-11-11 11:35 ` [char-misc-next 0/3] mei: driver cleanups Winkler, Tomas
2013-11-11 15:02   ` gregkh
2013-11-11 15:14     ` Winkler, Tomas [this message]

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=5B8DA87D05A7694D9FA63FD143655C1B1AF0929D@HASMSX106.ger.corp.intel.com \
    --to=tomas.winkler@intel.com \
    --cc=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®