From: Greg KH <gregkh@linuxfoundation.org>
To: Hans Wennborg <hans@hanshq.net>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192ee: fix %d confusingly prefixed with 0x in format strings
Date: Sun, 17 Aug 2014 09:49:38 -0700 [thread overview]
Message-ID: <20140817164938.GA28632@kroah.com> (raw)
In-Reply-To: <1407727722-28095-2-git-send-email-hans@hanshq.net>
On Sun, Aug 10, 2014 at 08:28:42PM -0700, Hans Wennborg wrote:
> Signed-off-by: Hans Wennborg <hans@hanshq.net>
> ---
> drivers/staging/rtl8192ee/pci.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
This patch doesn't apply at all to my tree, can you please refresh it
against the next linux-next tree and resend?
thanks,
greg k-h
prev parent reply other threads:[~2014-08-17 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 0:20 [PATCH 16/19] staging: rtl8192ee: fix %d confusingly prefixed with 0x in format strings Hans Wennborg
2014-08-10 4:23 ` Greg KH
2014-08-11 3:28 ` Hans Wennborg
2014-08-11 3:28 ` Hans Wennborg
2014-08-11 3:28 ` [PATCH] " Hans Wennborg
2014-08-17 16:49 ` 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=20140817164938.GA28632@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=hans@hanshq.net \
--cc=linux-kernel@vger.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