public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
	devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	trivial@kernel.org
Subject: Re: hv: Trivial cleanups for drivers/hv/connection.c
Date: Mon, 13 Jan 2014 15:02:00 -0800	[thread overview]
Message-ID: <20140113230200.GA3482@kroah.com> (raw)
In-Reply-To: <20131231215236.GA18573@amd.pavel.ucw.cz>

On Tue, Dec 31, 2013 at 10:52:37PM +0100, Pavel Machek wrote:
> __u32 is only useful for kernel-user interface, u32 should be enough
> for kernel. Formatting was very confusing around __get_free_pages().
> 
> Signed-off-by: Pavel Machek <pavel@ucw.cz>

This doesn't apply to my char-misc.git tree, care to redo it after
3.14-rc1 is out so that we can properly sync up?

thanks,

greg k-h

      parent reply	other threads:[~2014-01-13 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 21:52 Trivial cleanups for drivers/hv/connection.c Pavel Machek
2014-01-02 15:06 ` Dan Carpenter
2014-01-13 23:02 ` Greg KH [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=20140113230200.GA3482@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=trivial@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