linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: SPI bugfixes during Grant's sabbatical
Date: Sat, 26 Nov 2011 23:06:38 +0100	[thread overview]
Message-ID: <20111126220638.GA21603@pengutronix.de> (raw)

Hi,

so, Grant is on an engineering sabbatical and I promised to take care of SPI
during that time. While I was wondering why I did not see any relevant patches
so far, I just noticed I had been moved off the list without me noticing :(
(and now I need several tries to get this mail through, as well)

So, until Grant comes back, please CC me on SPI related bugfix patches for 3.2.
which should go to Linus. Please resend any bugfixes since 3.2-rc1, although I
will go through the backpile as well. I can also setup a spi-next branch in
which I could pick up new drivers or features for 3.3 if those got at least a
slight review from the list. If I missed such patches, let me know as well. I
can do a bit of review, but I definately need help from the list for that.

All the best,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

                 reply	other threads:[~2011-11-26 22:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111126220638.GA21603@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).