From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Fabio Estevam <festevam@gmail.com>,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] bcm/CmHost.c: Fix noisy compile warnings
Date: Wed, 15 Oct 2014 11:56:19 -0700 [thread overview]
Message-ID: <1413399379.7484.5.camel@perches.com> (raw)
In-Reply-To: <1413399256.2412.27.camel@jtkirshe-mobl>
On Wed, 2014-10-15 at 11:54 -0700, Jeff Kirsher wrote:
> On Wed, 2014-10-15 at 15:24 -0300, Fabio Estevam wrote:
> > On Wed, Oct 15, 2014 at 2:42 PM, Jeff Kirsher
> > <jeffrey.t.kirsher@intel.com> wrote:
> >
> > > I like the idea, but won't this exclude other 32 bit systems like MIPS
> > > and I am sure there might be others. I could assume that Beceem WIMAX
> > > was intended for x86 arch's that are 32 bit only, which may be a safe
> > > bet. The only thing we know for sure is that is broken on 64bit.
> >
> > What about this?
>
> That works for me. I am putting together a v2 patch now, since you came
> up with the change, I will put you as the author Fabio, ok?
Good idea.
next prev parent reply other threads:[~2014-10-15 18:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 12:26 [PATCH] bcm/CmHost.c: Fix noisy compile warnings Jeff Kirsher
2014-10-15 12:33 ` Joe Perches
2014-10-15 12:34 ` Dan Carpenter
2014-10-15 12:59 ` Dan Carpenter
2014-10-15 13:03 ` Jeff Kirsher
2014-10-15 16:11 ` Joe Perches
2014-10-15 17:42 ` Jeff Kirsher
2014-10-15 18:24 ` Fabio Estevam
2014-10-15 18:54 ` Jeff Kirsher
2014-10-15 18:56 ` Joe Perches [this message]
2014-10-15 18:56 ` Fabio Estevam
2014-10-15 19:53 ` Dan Carpenter
2014-10-15 20:03 ` Joe Perches
2014-10-16 7:48 ` Dan Carpenter
2014-10-16 7:54 ` Jeff Kirsher
2014-10-15 21:41 ` Matthias Beyer
2014-10-15 22:19 ` Jeff Kirsher
2014-10-15 22:24 ` Matthias Beyer
2014-10-15 22:41 ` Jeff Kirsher
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=1413399379.7484.5.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--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