public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johannes Schilling <of82ecuq@cip.cs.fau.de>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Kurt Kanzenbach <shifty91@gmail.com>,
	linux-kernel@i4.cs.fau.de, Al Cho <acho@novell.com>,
	Amarjargal Gundjalam <amarjargal16@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Laura Lawniczak <laura.lawniczak@googlemail.com>
Subject: Re: [PATCH 0/6] keucr: checkpatch fixes
Date: Thu, 6 Jun 2013 11:47:34 -0700	[thread overview]
Message-ID: <20130606184734.GA7548@kroah.com> (raw)
In-Reply-To: <1370535050-7167-1-git-send-email-of82ecuq@cip.cs.fau.de>

On Thu, Jun 06, 2013 at 06:10:44PM +0200, Johannes Schilling wrote:
> hi,
> 
> did some improvement on our previous patch series, see the more detailed
> replies below.

When you resend patches, please put "v2" in the subject lines, so I know
to take these over the previous ones.

thanks,

greg k-h

      parent reply	other threads:[~2013-06-06 18:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  8:50 [PATCH 0/6] keucr: checkpatch fixes Johannes Schilling
2013-06-05  8:50 ` [PATCH 1/6] keucr: remove some unneccesary typedefs Johannes Schilling
2013-06-05  9:25   ` Dan Carpenter
2013-06-05  8:50 ` [PATCH 2/6] keucr: fix some camelCase warnings Johannes Schilling
2013-06-05  9:23   ` Dan Carpenter
2013-06-05  9:48     ` Dan Carpenter
2013-06-05  8:50 ` [PATCH 3/6] keucr: migrate printk to dev_dbg/info/warn/err Johannes Schilling
2013-06-05  9:32   ` Dan Carpenter
2013-06-05  8:50 ` [PATCH 4/6] keucr: make error messages less aggressive Johannes Schilling
2013-06-05  9:36   ` Dan Carpenter
2013-06-05  8:50 ` [PATCH 5/6] keucr: fix some alignment- and whitespace-problems Johannes Schilling
2013-06-05  8:50 ` [PATCH 6/6] keucr: use more specific max_t(int, Johannes Schilling
2013-06-05  9:45   ` Dan Carpenter
2013-06-06 16:10     ` [PATCH 0/6] keucr: checkpatch fixes Johannes Schilling
2013-06-06 16:10       ` [PATCH 1/6] keucr: remove some unneccesary typedefs Johannes Schilling
2013-06-06 16:10       ` [PATCH 2/6] keucr: use more specific max_t(int, Johannes Schilling
2013-06-06 16:10       ` [PATCH 3/6] keucr: migrate printk to dev_dbg/info/warn/err Johannes Schilling
2013-06-06 17:53         ` Joe Perches
2013-06-06 21:11           ` Dan Carpenter
2013-06-06 21:23             ` Joe Perches
2013-06-06 22:07               ` Dan Carpenter
2013-06-06 21:14         ` Dan Carpenter
2013-06-06 16:10       ` [PATCH 4/6] keucr: more readable and friendly error messages Johannes Schilling
2013-06-06 21:48         ` Dan Carpenter
2013-06-06 16:10       ` [PATCH 5/6] keucr: moved function to other file Johannes Schilling
2013-06-06 21:23         ` Dan Carpenter
2013-06-06 16:10       ` [PATCH 6/6] keucr: fix some alignment- and whitespace-problems Johannes Schilling
2013-06-06 18:03         ` Joe Perches
2013-06-06 21:44         ` Dan Carpenter
2013-06-06 18:47       ` Greg Kroah-Hartman [this message]

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=20130606184734.GA7548@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=acho@novell.com \
    --cc=amarjargal16@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=laura.lawniczak@googlemail.com \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=of82ecuq@cip.cs.fau.de \
    --cc=shifty91@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