public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Daniel Mack <daniel@caiaq.de>,
	Vladimir Barinov <vbarinov@embeddedalley.com>,
	Linux MTD list <linux-mtd@lists.infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: mxc_nand: fix built breakage
Date: Thu, 14 May 2009 10:01:19 +0300	[thread overview]
Message-ID: <1242284479.27996.196.camel@localhost.localdomain> (raw)
In-Reply-To: <20090514065611.GU29278@pengutronix.de>

On Thu, 2009-05-14 at 08:56 +0200, Sascha Hauer wrote:
> On Wed, May 13, 2009 at 06:11:54PM +0200, Daniel Mack wrote:
> > On Wed, May 13, 2009 at 08:09:43PM +0400, Vladimir Barinov wrote:
> > > Please find the patch that I've sent some time ago. This patch should  
> > > fix the issue you described.
> > > http://lists.infradead.org/pipermail/linux-mtd/2009-April/025363.html
> > 
> > 
> > Ah, ok, thanks.
> > 
> > Did anyone pick it up for mainline already?
> > Sascha, I didn't see that one in your tree either.
> 
> It seems to be pure luck when the patches on the mtd list get picked up.
> Most of the time I do not even a reaction from the list or David. I
> wonder if someone will beat me up when I take the i.MX nand patches via
> my arm tree.

I've put Vladimir's patch to my l2-mtd-2.6.git tree:
http://git.infradead.org/users/dedekind/l2-mtd-2.6.git

which means I'll be pinging David about pulling it. This is all
I can do for you, unfortunately.

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


  reply	other threads:[~2009-05-14  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 15:43 [PATCH] mtd: mxc_nand: fix built breakage Daniel Mack
2009-05-13 15:47 ` Daniel Mack
2009-05-13 16:09 ` Vladimir Barinov
2009-05-13 16:11   ` Daniel Mack
2009-05-14  6:56     ` Sascha Hauer
2009-05-14  7:01       ` Artem Bityutskiy [this message]
2009-05-14  7:45         ` Sascha Hauer

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=1242284479.27996.196.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=daniel@caiaq.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=vbarinov@embeddedalley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox