From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Oleg Drokin <green@linuxhacker.ru>, Joe Perches <joe@perches.com>,
driverdevel <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 5/5] lustre: add myself to list of people to CC on lustre patches
Date: Wed, 29 Jan 2014 05:02:36 -0800 [thread overview]
Message-ID: <20140129130236.GC1727@kroah.com> (raw)
In-Reply-To: <CAMuHMdWi4KPYa6GmkSgjxpL-mMxJB5FHG2FuoQ7UEWNpEqt-9g@mail.gmail.com>
On Tue, Jan 28, 2014 at 08:28:33PM +0100, Geert Uytterhoeven wrote:
> On Sat, Jan 25, 2014 at 4:23 AM, Oleg Drokin <green@linuxhacker.ru> wrote:
> > On Jan 24, 2014, at 3:55 AM, Geert Uytterhoeven wrote:
> >> On Fri, Jan 24, 2014 at 6:51 AM, Oleg Drokin <green@linuxhacker.ru> wrote:
> >>>> +STAGING - LUSTRE
> >>>> +M: Andreas Dilger <andreas.dilger@intel.com>
> >>>> +M: Oleg Drokin <oleg.drokin@intel.com>
> >>>> +M: Peng Tao <tao.peng@emc.com>.
> >>>> +L: hpdd-discuss <hpdd-discuss@lists.01.org>
> >>>> +S: Odd Fixes
> >>>
> >>> Actually we are at least Maintained here, if not outright Supported.
> >>
> >> Good to hear that!
> >> So can we assume that https://lkml.org/lkml/2013/9/9/725 will be fixed
> >> shortly,
> >
> > We are working on it.
>
> Thanks!
>
> >> and http://kisskb.ellerman.id.au/kisskb/buildresult/10508264/
> >> will turn green again?
> >
> > I certainly hope so.
> > BTW, do you also provide interface where I can drop in my patch and your builder verify it for me by any chance,
>
> It's called linux-next, but Lustre is part of staging, which is already
> included. No idea how lustre gets updated in thes staging tree, though.
Like any other patch that gets sent to drivers/staging, through my
staging.git tree.
next prev parent reply other threads:[~2014-01-29 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 4:45 [PATCH 0/5] Lustre fixes from my testing Oleg Drokin
2014-01-24 4:45 ` [PATCH 1/5] staging/lustre: fix compile warning with is_vmalloc_addr Oleg Drokin
2014-01-24 4:45 ` [PATCH 2/5] staging/lustre/lnet: Fix use after free in ksocknal_send Oleg Drokin
2014-01-24 4:45 ` [PATCH 3/5] lustre: Account for changelog_ext_rec in CR_MAXSIZE Oleg Drokin
2014-01-24 4:45 ` [PATCH 4/5] lustre: Correct KUC code max changelog msg size Oleg Drokin
2014-01-24 4:45 ` [PATCH 5/5] lustre: add myself to list of people to CC on lustre patches Oleg Drokin
2014-01-24 5:44 ` Joe Perches
2014-01-24 5:51 ` Oleg Drokin
2014-01-24 8:55 ` Geert Uytterhoeven
2014-01-25 3:23 ` Oleg Drokin
2014-01-28 19:28 ` Geert Uytterhoeven
2014-01-29 13:02 ` Greg Kroah-Hartman [this message]
2014-03-26 8:44 ` Geert Uytterhoeven
2014-03-26 9:02 ` Christoph Hellwig
2014-03-26 16:10 ` Oleg Drokin
2014-01-24 8:12 ` Dan Carpenter
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=20140129130236.GC1727@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=green@linuxhacker.ru \
--cc=hch@infradead.org \
--cc=joe@perches.com \
--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.