From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Cc: Martyn Welch <martyn.welch@ge.com>,
devel@driverdev.osuosl.org, Igor Alekseev <igor.alekseev@itep.ru>,
linux-kernel@vger.kernel.org,
Manohar Vanga <manohar.vanga@gmail.com>
Subject: Re: [PATCH 0/3] VME bus error handling overhaul
Date: Wed, 16 Sep 2015 08:53:13 -0700 [thread overview]
Message-ID: <20150916155313.GA9488@kroah.com> (raw)
In-Reply-To: <E8D69262-AEDC-4A38-A91E-048FE2D42CB3@gmail.com>
On Wed, Sep 16, 2015 at 11:39:22AM -0400, Dmitry Kalinkin wrote:
>
> > On 05 Aug 2015, at 16:12, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Jul 06, 2015 at 01:31:47PM +0100, Martyn Welch wrote:
> >> Hi Dmitry,
> >>
> >> These are looking good to me.
> >
> > Can I get an "Acked-by:" or something so that I know it's ok to apply
> > these?
> >
> > thanks,
> >
> > greg k-h-
>
> Now that we have next cycle, should I resend these?
That would be good.
next prev parent reply other threads:[~2015-09-16 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 14:11 [PATCH 0/3] VME bus error handling overhaul Dmitry Kalinkin
2015-07-02 14:11 ` [PATCH 1/3] vme: move tsi148 error handling into VME subsystem Dmitry Kalinkin
2015-07-02 14:11 ` [PATCH 2/3] vme: include address space in error filtering Dmitry Kalinkin
2015-07-02 14:11 ` [PATCH 3/3] vme: change bus error handling scheme Dmitry Kalinkin
2015-07-06 12:31 ` [PATCH 0/3] VME bus error handling overhaul Martyn Welch
2015-07-06 14:20 ` Dmitry Kalinkin
2015-07-06 14:43 ` [PATCH] vme: print unhandled VME access errors Dmitry Kalinkin
2015-07-06 14:50 ` Martyn Welch
2015-08-05 20:12 ` [PATCH 0/3] VME bus error handling overhaul Greg Kroah-Hartman
2015-09-16 15:39 ` Dmitry Kalinkin
2015-09-16 15:53 ` Greg Kroah-Hartman [this message]
2015-09-16 15:55 ` Dmitry Kalinkin
2015-09-16 18:18 ` Dmitry Kalinkin
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=20150916155313.GA9488@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dmitry.kalinkin@gmail.com \
--cc=igor.alekseev@itep.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@gmail.com \
--cc=martyn.welch@ge.com \
/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.