public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ravishankar <ravishankarkm32@gmail.com>
Cc: gregkh@suse.de, wfp5p@virginia.edu, devel@driverdev.osuosl.org,
	Ravishankar <ravishankarkm32@gmal.com>,
	linux-kernel@vger.kernel.org,
	Ravishankar <ravi.shankar@greenturtles.in>
Subject: Re: [PATCH] Staging: comedi: fix printk issue in adv_pci1710.c
Date: Tue, 23 Aug 2011 11:53:22 -0700	[thread overview]
Message-ID: <20110823185322.GA11386@kroah.com> (raw)
In-Reply-To: <1313761468-8055-1-git-send-email-ravishankarkm32@gmail.com>

On Fri, Aug 19, 2011 at 09:44:28AM -0400, Ravishankar wrote:
> From: Ravishankar <ravi.shankar@greenturtles.in>
> 
> This is a patch to the adv_pci1710.c file that fixes up a printk warning found by the checkpatch.pl tool
> 
> Signed-off-by: Ravishankar <ravishankarkm32@gmal.com>

Due to the huge number of different revisions of your patches, and the
lack of any response from you based on the review comments except to
send more patches, I've dropped everything from you that was in my
to-apply queue.

Can you please resend everything that I have not applied, that is still
applicable, after handling the review comments of the numerous people
who took their time to try to help you out here?  To ignore them is not
nice at all.

thanks,

greg k-h

  reply	other threads:[~2011-08-23 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH]Staging: comedi: fix printk warning issue in adv_pci1710.c>
2011-08-19 13:44 ` [PATCH] Staging: comedi: fix printk issue in adv_pci1710.c Ravishankar
2011-08-23 18:53   ` Greg KH [this message]
     [not found] <[PATCH]Staging: comedi: fix warning issue in adv_pci1710.c>
2011-08-11  5:25 ` [PATCH] Staging: comedi: fix printk() " Ravishankar

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=20110823185322.GA11386@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravi.shankar@greenturtles.in \
    --cc=ravishankarkm32@gmail.com \
    --cc=ravishankarkm32@gmal.com \
    --cc=wfp5p@virginia.edu \
    /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