public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drivers/misc/sgi-gru: unapplied patches and a new one
Date: Wed, 23 Sep 2015 12:48:25 -0500	[thread overview]
Message-ID: <20150923174825.GB20215@sgi.com> (raw)
In-Reply-To: <1442830699-20562-1-git-send-email-sudipm.mukherjee@gmail.com>

Sudip,

I can take a look at the Jack Steiner patches.  Was there anything in the set
of 3 patches that you sent that still needs a review?

On Mon, Sep 21, 2015 at 03:48:16PM +0530, Sudip Mukherjee wrote:
> Hi Dimitri,
> I have taken these patches which were having ACK from you. Apart from
> these I saw another series of 25 patches from Jack Steiner <steiner@sgi.com>
> which will still apply almost cleanly but there was no ACK or review.
> Can you please have a look at: https://lkml.org/lkml/2010/7/19/289
> or if you want I can take them and mail to you.
> 
> Hi Greg,
> As discussed the first two are the old unapplied patches with maintainer
> ACK. I have mentioned the reference url individually in each patch for
> your verification. I have only considered those which are having
> maintainer ACK.
> The last patch is a new one by me. There was another pending patch with
> maintainer ACK but that patch will not apply and is not relevant now.
> But the error which my new patch solves was found while checking that
> old patch.
> 
> Ohhh .. and there was also one more old patch from 2009, git log shows
> that also was not applied. Just guess who the submitter was ......
> 
> gregkh@suse.de  :)
> 
> reference at: https://patchwork.kernel.org/patch/58189/
> 
> regards
> sudip
> 
> Manuel Schölling (1):
>   sgi-gru: use time_before()
> 
> Rickard Strandqvist (1):
>   misc: sgi-gru: gruhandles.c: Remove unused function
> 
> Sudip Mukherjee (1):
>   drivers/misc/sgi-gru: fix return of error
> 
>  drivers/misc/sgi-gru/gruhandles.c  |  6 ------
>  drivers/misc/sgi-gru/gruhandles.h  |  1 -
>  drivers/misc/sgi-gru/grumain.c     |  4 +++-
>  drivers/misc/sgi-gru/grutlbpurge.c | 20 ++++++++++----------
>  4 files changed, 13 insertions(+), 18 deletions(-)
> 
> -- 
> 1.9.1

  parent reply	other threads:[~2015-09-23 17:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 10:18 [PATCH 0/3] drivers/misc/sgi-gru: unapplied patches and a new one Sudip Mukherjee
2015-09-21 10:18 ` [PATCH 1/3] sgi-gru: use time_before() Sudip Mukherjee
2015-09-21 10:18 ` [PATCH 2/3] misc: sgi-gru: gruhandles.c: Remove unused function Sudip Mukherjee
2015-09-21 10:18 ` [PATCH 3/3] drivers/misc/sgi-gru: fix return of error Sudip Mukherjee
2015-09-26 12:44   ` Dimitri Sivanich
2015-09-23 17:48 ` Dimitri Sivanich [this message]
2015-09-24  7:01   ` [PATCH 0/3] drivers/misc/sgi-gru: unapplied patches and a new one Sudip Mukherjee
2015-10-05 15:13     ` Sudip Mukherjee
2015-10-05 15:18       ` Dimitri Sivanich
2015-10-14  4:52         ` Sudip Mukherjee
2015-10-14 14:33           ` Dimitri Sivanich
2015-10-26  9:15             ` Sudip Mukherjee

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=20150923174825.GB20215@sgi.com \
    --to=sivanich@sgi.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox