From: Mike Frysinger <vapier.adi@gmail•com>
To: Greg KH <greg@kroah•com>
Cc: Greg Kroah-Hartman <gregkh@suse•de>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Lothar Wassmann <LW@karo-electronics•de>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [PATCH] USB: isp1362: fix build warnings on 64-bit systems
Date: Tue, 6 Oct 2009 04:32:29 -0400 [thread overview]
Message-ID: <8bd0f97a0910060132r1dd6b6a4u71eaa8763862aebd@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0908131734h2588d240k9000bace38b58e7f@mail.gmail.com>
On Thu, Aug 13, 2009 at 20:34, Mike Frysinger wrote:
> On Thu, Aug 13, 2009 at 19:44, Greg KH wrote:
>> On Tue, Aug 11, 2009 at 11:00:53PM -0400, Mike Frysinger wrote:
>>> A bunch of places assumed pointers were 32-bits in size (bit checking and
>>> debug output), but none of these affected runtime functionality.
>>>
>>> Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
>>> Signed-off-by: Mike Frysinger <vapier@gentoo•org>
>>
>> This patch doesn't apply to my tree, what did you make it against?
>
> it was reported against next, so i used that
so what tree do i need to use to get you to merge this ? i'm guessing
the semantic patch was what caused conflicts (my proposed patch
already included that fix, but too late now).
-mike
next prev parent reply other threads:[~2009-10-06 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 3:00 [PATCH] USB: isp1362: fix build warnings on 64-bit systems Mike Frysinger
2009-08-13 23:44 ` Greg KH
2009-08-14 0:34 ` Mike Frysinger
2009-10-06 8:32 ` Mike Frysinger [this message]
2009-10-06 14:34 ` Greg KH
2009-10-07 8:29 ` [PATCH v2] " Mike Frysinger
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=8bd0f97a0910060132r1dd6b6a4u71eaa8763862aebd@mail.gmail.com \
--to=vapier.adi@gmail$(echo .)com \
--cc=LW@karo-electronics$(echo .)de \
--cc=greg@kroah$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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