mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH] staging/dt3155: fix build error caused by {write|read}l change
Date: Thu, 8 Apr 2010 12:11:23 -0700	[thread overview]
Message-ID: <20100408191123.GB31571@kroah.com> (raw)
In-Reply-To: <201003031124.06345.hartleys@visionengravers.com>

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.

Can you respin all of them please?

thanks,

greg k-h

  reply	other threads:[~2010-04-08 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 18:24 H Hartley Sweeten
2010-04-08 19:11 ` Greg KH [this message]
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

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=20100408191123.GB31571@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome