Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/9] ARM: S5PV210: I2S: Upgrade platform device (Action Required)
Date: Tue, 16 Nov 2010 11:17:17 +0000	[thread overview]
Message-ID: <20101116111717.GM12986@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <213935334.90145.1289905638298.JavaMail.prod@app013.dmz>

On Tue, Nov 16, 2010 at 03:07:18AM -0800, noreply at boxbe.com wrote:
> 
> Hello Mark Brown,
> 
> Your message about "Re: [PATCH 8/9] ARM: S5PV210: I2S: Upgrade platform device" 
> has been waitlisted.  
> 
> Please add yourself to my Boxbe Guest List so your messages will 
> go to my Inbox. 
> 
> Click the link below to be added:
> https://www.boxbe.com/crs?tc=5918369326_224329907

Your software is generating these messages in response to mails posted
to public mailing lists and not directed specifically at you.  Please
disable this software, it is generating noise for community members.

           reply	other threads:[~2010-11-16 11:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <213935334.90145.1289905638298.JavaMail.prod@app013.dmz>]

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=20101116111717.GM12986@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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