From: Greg KH <greg@kroah.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"ss@aao.gov.au" <ss@aao.gov.au>
Subject: Re: [PATCH] staging/dt3155: fix build error caused by {write|read}l change
Date: Tue, 13 Apr 2010 22:13:55 -0700 [thread overview]
Message-ID: <20100414051355.GC17429@kroah.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636D5B7876@AUSP01VMBX24.collaborationhost.net>
On Tue, Apr 13, 2010 at 07:50:51PM -0500, H Hartley Sweeten wrote:
> On Thursday, April 08, 2010 1:46 PM, Greg KH wrote:
> > On Thu, Apr 08, 2010 at 03:38:06PM -0500, H Hartley Sweeten wrote:
> >> On Thursday, April 08, 2010 12:11 PM, Greg KH wrote:
> >>> On Wed, Mar 03, 2010 at 11:24:06AM -0700, H Hartley Sweeten wrote:
> >>>> This fixes a build error caused by replacing {Write | Read}MReg with
> >>>> {write | read}l.
> >>>
> >>> Ick, can you merge this with your other patch so we don't have build
> >>> errors? I just hit this and I had to drop all of your patches.
> >>
> >> I was expecting you to NAK all of them anyway after I saw all the code
> >> cleanup patches coming in on LKML.
> >>
> >>> Can you respin all of them please?
> >>
> >> Not a problem. Are you planning on merging any of the dt3155 cleanup
> >> patches? If so I will wait until they show up.
> >
> > I took some, you should have gotten the responses now.
>
> Hello Greg,
>
> Do you know off hand what (if any) of the dt3155 patches you took and when
> they might show up in linux-next? The last commits in next-20100413 are:
>
> commit 5a0e3ad6af8660be21ca98a971cd00f331318c05
> Author: Tejun Heo <tj@kernel.org>
> Date: Wed Mar 24 17:04:11 2010 +0900
>
> include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from p
>
> commit 3a8954e8f22cf31791d8c524c2839433e39f9368
> Author: H Hartley Sweeten <hartleys@visionengravers.com>
> Date: Fri Feb 26 17:58:07 2010 -0700
>
> staging: dt3155: revert u_long to u64 usage
Hm, I need to tell Stephen to pull the proper tree for my staging-next
stuff, I am playing around with just using git for it. Give me some
time, I'm in a conference all this week...
thanks,
greg k-h
prev parent reply other threads:[~2010-04-14 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 18:24 [PATCH] staging/dt3155: fix build error caused by {write|read}l change H Hartley Sweeten
2010-04-08 19:11 ` Greg KH
2010-04-08 20:38 ` H Hartley Sweeten
2010-04-08 20:46 ` Greg KH
2010-04-08 21:07 ` H Hartley Sweeten
2010-04-14 0:50 ` H Hartley Sweeten
2010-04-14 5:13 ` 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=20100414051355.GC17429@kroah.com \
--to=greg@kroah.com \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ss@aao.gov.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.