All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Andersson <jan@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: add {read,write}*_be routines
Date: Mon, 16 May 2011 07:57:28 +0000	[thread overview]
Message-ID: <4DD0D8E8.4080802@gaisler.com> (raw)
In-Reply-To: <1305105213-31675-1-git-send-email-jan@gaisler.com>

On 05/12/2011 10:45 PM, David Miller wrote:
> From: Jan Andersson <jan@gaisler.com>
> Date: Wed, 11 May 2011 11:13:33 +0200
> 
>> This patch adds {read,write}*_be big endian memory access
>> routines to the io.h header used on SPARC32 and SPARC64.
>>
>> Tested on SPARC32 (LEON)
>>
>> Signed-off-by: Jan Andersson <jan@gaisler.com>
> 
> Applied, thanks Jan.

Thanks David. Will this show up in sparc-next? Any chance that you could
update the tree on kernel.org? I was asked to provide identification of
the commit so that it could be merged into usb-next - in order for me to
get another patchset accepted.

Best regards,
  Jan

  parent reply	other threads:[~2011-05-16  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11  9:13 [PATCH] sparc: add {read,write}*_be routines Jan Andersson
2011-05-12 20:45 ` David Miller
2011-05-16  7:57 ` Jan Andersson [this message]
2011-05-16 15:10 ` David Miller

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=4DD0D8E8.4080802@gaisler.com \
    --to=jan@gaisler.com \
    --cc=sparclinux@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 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.