From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peng Tao <bergwolf@gmail.com>
Cc: "Dilger, Andreas" <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 07/11] staging/lustre: fix build error on non-x86 platforms
Date: Wed, 26 Jun 2013 10:28:17 -0700 [thread overview]
Message-ID: <20130626172817.GB6842@kroah.com> (raw)
In-Reply-To: <CA+a=Yy48DH0q7-m8J0r-0oBGLbEBx5AwrBKCEb2pZ3AsPJg-Xw@mail.gmail.com>
On Wed, Jun 26, 2013 at 04:52:03PM +0800, Peng Tao wrote:
> Since it takes time to patch kernel's generic watchdog, can we get
> this patch in so that we have a build-able Lustre base, and then we
> can work on push necessary bits to kernel watchdog? I understand that
> we shouldn't reinvent things. Just don't want it to be a blocking
> issue for build and if we simply delete it, we lose a feature that is
> still missing in kernel watchdog.
Why not delete it, and then work on getting the feature into the
upstream watchdog? Given that this stuff isn't going to be enabled
until 3.12 anyway, you have time, right?
Shortcuts aren't really allowed in upstream kernel development, you know
that :)
thanks,
greg k-h
next prev parent reply other threads:[~2013-06-26 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372119326-3565-1-git-send-email-bergwolf@gmail.com>
[not found] ` <1372119326-3565-8-git-send-email-bergwolf@gmail.com>
[not found] ` <20130625022244.GG18752@kroah.com>
[not found] ` <CA+a=Yy6GD6xAG=qULGbwOA1wCt-seVtCv1tufGvmmO-jpbgL3A@mail.gmail.com>
[not found] ` <220AF645-E299-4B35-9E15-858C7A10FF3E@intel.com>
[not found] ` <20130625152003.GB20244@kroah.com>
2013-06-26 8:52 ` Peng Tao
2013-06-26 17:28 ` Greg Kroah-Hartman [this message]
2013-06-28 20:25 ` Dilger, Andreas
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=20130626172817.GB6842@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.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 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®