All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Linux MTD <linux-mtd@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch/rfc 2.6.29 2/2] MTD: support driver model updates
Date: Wed, 01 Apr 2009 09:48:08 +0300	[thread overview]
Message-ID: <1238568488.20906.34.camel@localhost.localdomain> (raw)
In-Reply-To: <200903312342.24019.david-b@pacbell.net>

On Tue, 2009-03-31 at 23:42 -0700, David Brownell wrote:
> On Tuesday 31 March 2009, Artem Bityutskiy wrote:
> > OK. MTD long needs sysfs, and I'm very happy with this
> > patches, even though they are not 100% complete. Good
> > start anyway.
> > 
> > Acked-by: Artem Bityutskiy <dedekind@infradead.org>
> 
> Thanks.  I'll expect someone to handle getting these
> merged through the MTD tree, then.

David Woodhouse maintains the MTD tree. He saw your patches,
not sure when he takes them.

> And I'll be rather surprised if no more attributes
> appear by the time this gets to mainline!  :)

If he merges them during this merge window, then this might
not be the case :-)

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch/rfc 2.6.29 2/2] MTD: support driver model updates
Date: Wed, 01 Apr 2009 09:48:08 +0300	[thread overview]
Message-ID: <1238568488.20906.34.camel@localhost.localdomain> (raw)
In-Reply-To: <200903312342.24019.david-b@pacbell.net>

On Tue, 2009-03-31 at 23:42 -0700, David Brownell wrote:
> On Tuesday 31 March 2009, Artem Bityutskiy wrote:
> > OK. MTD long needs sysfs, and I'm very happy with this
> > patches, even though they are not 100% complete. Good
> > start anyway.
> > 
> > Acked-by: Artem Bityutskiy <dedekind@infradead.org>
> 
> Thanks.  I'll expect someone to handle getting these
> merged through the MTD tree, then.

David Woodhouse maintains the MTD tree. He saw your patches,
not sure when he takes them.

> And I'll be rather surprised if no more attributes
> appear by the time this gets to mainline!  :)

If he merges them during this merge window, then this might
not be the case :-)

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)


  reply	other threads:[~2009-04-01  6:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903260039.34013.david-b@pacbell.net>
2009-03-26  7:42 ` [patch/rfc 2.6.29 2/2] MTD: support driver model updates David Brownell
2009-04-01  5:46   ` Artem Bityutskiy
2009-04-01  5:46     ` Artem Bityutskiy
2009-04-01  5:57     ` David Brownell
2009-04-01  5:57       ` David Brownell
2009-04-01  6:10       ` Artem Bityutskiy
2009-04-01  6:10         ` Artem Bityutskiy
2009-04-01  6:42         ` David Brownell
2009-04-01  6:42           ` David Brownell
2009-04-01  6:48           ` Artem Bityutskiy [this message]
2009-04-01  6:48             ` Artem Bityutskiy
2009-04-01  6:08     ` Vitaly Wool

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=1238568488.20906.34.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=david-b@pacbell.net \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@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 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.