From: Greg KH <gregkh@linuxfoundation.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Tomas Winkler <tomas.winkler@intel.com>,
arnd@arndb.de, alan@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next V2] mei: drop the warning when cl is not initialized during unlinking
Date: Mon, 14 Jan 2013 07:12:20 -0800 [thread overview]
Message-ID: <20130114151220.GA20610@kroah.com> (raw)
In-Reply-To: <CA+icZUXLFp_oZnVPcVDwuy_dvbywKgqHKknzg6qyF3o=mw-p+A@mail.gmail.com>
On Mon, Jan 14, 2013 at 03:55:44PM +0100, Sedat Dilek wrote:
> On Mon, Jan 14, 2013 at 3:32 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Jan 14, 2013 at 03:14:50PM +0100, Sedat Dilek wrote:
> >> On Thu, Jan 10, 2013 at 4:32 PM, Tomas Winkler <tomas.winkler@intel.com> wrote:
> >>
> >> Can you please apply this patch to char-misc-next?
> >> I am hitting it again while doing other regression testing!
> >
> > Please be patient, it will get there soon.
> >
>
> The same answer I got for the report/testing of [1], it is still not
> in mainline.
> Yes, I have seen your pull-request for char-misc-linus of today, but
> why does this takes weeks to apply?
"Weeks"? You do realize this was sent to me over a holliday break, one
in which I was on vacation? I only returned a week ago, to over 1500
patches to sift through and process.
And, I did that within 4 days, and sent the needed fix off to Linus
within 7 days of returning.
If you think you can do better than that, wonderful, I would love for
you to start out reviewing code and helping with handling stuff like
that. Please do so before complaining about anything.
greg k-h
next prev parent reply other threads:[~2013-01-14 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:32 [char-misc-next V2] mei: drop the warning when cl is not initialized during unlinking Tomas Winkler
2013-01-14 14:14 ` Sedat Dilek
2013-01-14 14:32 ` Greg KH
2013-01-14 14:55 ` Sedat Dilek
2013-01-14 15:12 ` Greg KH [this message]
2013-01-14 15:34 ` Sedat Dilek
2013-01-15 1:46 ` Chen Gang F T
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=20130114151220.GA20610@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=tomas.winkler@intel.com \
--cc=torvalds@linux-foundation.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