public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, ulf.hansson@linaro.org
Cc: arik@wizery.com, david.gnedt@davizone.at, eliad@wizery.com,
	jan.nikitenko@gmail.com,
	laurent.pinchart+renesas@ideasonboard.com,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, luca@coelho.fi, pavel@ucw.cz,
	tony@atomide.com
Subject: Re: [PATCH 2/3] drivers/mmc/host/mmc_spi.c: Use get/put_unaligned_be32
Date: 14 May 2014 08:23:57 -0400	[thread overview]
Message-ID: <20140514122357.11052.qmail@ns.horizon.com> (raw)
In-Reply-To: <CAPDyKFo9xZ-z6eM0zG2A+=Bwj0EVyGxm=m28Lh9cHPSB+8qq1w@mail.gmail.com>

Ulf Hansson wrote:
> Feel free to take this through the wireless tree as well. I assumes
> it's that same patchset as the other spi related fixes?

I'd like to answer, but I'm not sure which "other spi related fixes"
you're referring to.  If you mean patches 1 and 3 of this series, then
obviously.  If you mean something else then probably not.

[PATCH 1/3] lib/crc7: Shift crc7() output left 1 bit
[PATCH 3/3] drivers/net/wireless/ti/wl*/spi.c: Simplify CRC computation


As there seems to be no objection to sending the mmc change via the
wireless tree, are they ready to be queued there?

The additional reviews are:
All 3: Reviewed-by: Pavel Machek <pavel@ucw.cz>
2/3: Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
2/3: Acked-by: Ulf Hansson <ulf.hansson@linaro.org>

I can resend everything with the additional signoff lines
if that's easier for you.

  reply	other threads:[~2014-05-14 12:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  4:35 [PATCH] lib/crc7: Shift crc7() output left 1 bit George Spelvin
2014-05-11  8:28 ` Pavel Machek
2014-05-11  9:16   ` George Spelvin
2014-05-14 19:56     ` Pavel Machek
2014-05-15  0:32       ` George Spelvin
2014-05-15  6:06         ` Pavel Machek
2014-05-11 10:02   ` [PATCH v2 1/3] " George Spelvin
2014-05-11 10:05     ` [PATCH 2/3] drivers/mmc/host/mmc_spi.c: Use get/put_unaligned_be32 George Spelvin
2014-05-11 10:33       ` Pavel Machek
2014-05-12  8:05       ` Geert Uytterhoeven
2014-05-14 10:17       ` Ulf Hansson
2014-05-14 12:23         ` George Spelvin [this message]
2014-05-14 12:30           ` Ulf Hansson
2014-05-14 14:50           ` John W. Linville
2014-05-11 10:07     ` [PATCH 3/3] drivers/net/wireless/ti/wl*/spi.c: Simplify CRC computation George Spelvin
2014-05-11 10:36       ` Pavel Machek
2014-05-11 10:32     ` [PATCH v2 1/3] lib/crc7: Shift crc7() output left 1 bit Pavel Machek
2014-05-14 10:14     ` Ulf Hansson
2014-05-15  0:37     ` H. Peter Anvin
2014-05-15  1:15       ` George Spelvin
2014-05-15  1:26         ` H. Peter Anvin
2014-05-15  2:02           ` George Spelvin

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=20140514122357.11052.qmail@ns.horizon.com \
    --to=linux@horizon.com \
    --cc=arik@wizery.com \
    --cc=david.gnedt@davizone.at \
    --cc=eliad@wizery.com \
    --cc=jan.nikitenko@gmail.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luca@coelho.fi \
    --cc=pavel@ucw.cz \
    --cc=tony@atomide.com \
    --cc=ulf.hansson@linaro.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