From: Duncan Sands <duncan.sands@gmail.com>
To: Seth Archer <learc83@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Usb: atm: usbatm: fixed a pointer variable format issue
Date: Fri, 06 Dec 2013 16:25:56 +0100 [thread overview]
Message-ID: <52A1EC84.3090703@gmail.com> (raw)
In-Reply-To: <CAFcs13FWknRxhT_ZUnirRk+O0ZeDq1TVFtgMD9hkp=aVKUnHLA@mail.gmail.com>
Hi Seth,
On 06/12/13 15:24, Seth Archer wrote:
> Sorry, but do you mean the patch is OK, or the original is OK and no patch
> necessary?
I meant that the patch is obviously OK.
Ciao, Duncan.
>
> -Seth
>
>
> On Fri, Dec 6, 2013 at 3:24 AM, Duncan Sands <duncan.sands@gmail.com
> <mailto:duncan.sands@gmail.com>> wrote:
>
> On 06/12/13 04:59, learc83 wrote:
>
> Fixed a pointer variable format issue.
>
>
> This is obviously OK.
prev parent reply other threads:[~2013-12-06 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 3:59 [PATCH] Usb: atm: usbatm: fixed a pointer variable format issue learc83
2013-12-06 8:24 ` Duncan Sands
[not found] ` <CAFcs13FWknRxhT_ZUnirRk+O0ZeDq1TVFtgMD9hkp=aVKUnHLA@mail.gmail.com>
2013-12-06 15:25 ` Duncan Sands [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=52A1EC84.3090703@gmail.com \
--to=duncan.sands@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=learc83@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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