All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: sedat.dilek@gmail.com, Sedat Dilek <sedat.dilek@googlemail.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Aug 1
Date: Tue, 2 Aug 2011 11:29:07 +1000	[thread overview]
Message-ID: <20110802112907.5ca1abdd81758bd3b0bb6321@canb.auug.org.au> (raw)
In-Reply-To: <20110801145422.cccff7aa.rdunlap@xenotime.net>

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

Hi all,

On Mon, 1 Aug 2011 14:54:22 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
>
> On Mon, 1 Aug 2011 09:01:21 +0200 Sedat Dilek wrote:
> 
> > Just FYI: mmotm-tree still misses the fixup-patch from [1].
> > 
> > [1] https://patchwork.kernel.org/patch/1021602/
> 
> Yes, I am applying this patch daily (among others).  :(
> 
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>

OK, I will apply this patch to linux-next as a merge fixup on top of
Andrew's tree.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-08-02  1:29 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01  4:47 linux-next: Tree for Aug 1 Stephen Rothwell
2011-08-01  7:01 ` Sedat Dilek
2011-08-01 21:54   ` Randy Dunlap
2011-08-02  1:29     ` Stephen Rothwell [this message]
2011-08-02 10:38       ` Sedat Dilek
2011-08-01 21:52 ` linux-next: Tree for Aug 1 (wireless/rt2x00) Randy Dunlap
2013-08-01  7:25 linux-next: Tree for Aug 1 Stephen Rothwell
2013-08-01  7:25 ` Stephen Rothwell
2013-08-01  7:50 ` Sedat Dilek
2014-08-01  9:14 Stephen Rothwell
2016-08-01  4:02 Stephen Rothwell
2017-08-01  7:37 Stephen Rothwell
2017-08-01 12:42 ` Sergey Senozhatsky
2017-08-01 13:20   ` Arnd Bergmann
2017-08-01 13:28     ` Arnd Bergmann
2017-08-01 23:55       ` Sergey Senozhatsky
2017-08-02 11:13         ` Arnd Bergmann
2018-08-01  7:58 Stephen Rothwell
2018-08-01 22:48 ` Guenter Roeck
2018-08-01 22:52   ` James Bottomley
2018-08-01 23:00     ` James Bottomley
2018-08-02  0:05       ` Stephen Rothwell
2018-08-02  1:19         ` Guenter Roeck
2018-08-01 23:47     ` Guenter Roeck
2018-08-01 23:57       ` Ming Lei
2018-08-02  0:03         ` James Bottomley
2018-08-02  0:20           ` Guenter Roeck
2018-08-02  4:58           ` Guenter Roeck
2018-08-02  5:04             ` Bart Van Assche
2018-08-02  5:04               ` Bart Van Assche
2018-08-02 12:46               ` Guenter Roeck
2018-08-02 12:46                 ` Guenter Roeck
2018-08-02 12:51                 ` Johannes Thumshirn
2018-08-02 12:51                   ` Johannes Thumshirn
2018-08-02 13:00                   ` Guenter Roeck
2018-08-02 13:00                     ` Guenter Roeck
2018-08-02 13:06                     ` Johannes Thumshirn
2018-08-02 13:06                       ` Johannes Thumshirn
2018-08-02 11:35             ` Ming Lei
2018-08-02 13:05               ` Guenter Roeck
2018-08-02 16:27                 ` Ming Lei
2018-08-02 16:40                   ` Bart Van Assche
2018-08-02 16:40                     ` Bart Van Assche
2018-08-02 16:50                     ` Ming Lei
2018-08-02 16:50                       ` Ming Lei
2018-08-02 16:57                       ` Bart Van Assche
2018-08-02 16:57                         ` Bart Van Assche
2018-08-02  0:12         ` Guenter Roeck
2019-08-01  6:14 Stephen Rothwell
2023-08-01  5:19 Stephen Rothwell

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=20110802112907.5ca1abdd81758bd3b0bb6321@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sboyd@codeaurora.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.com \
    /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.