public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] nand: Sync with Linux v4.1
Date: Wed, 05 Aug 2015 01:45:45 +0200	[thread overview]
Message-ID: <55C14EA9.6050008@denx.de> (raw)
In-Reply-To: <1438712768.2097.81.camel@freescale.com>

On 04.08.2015 20:26, Scott Wood wrote:
> On Tue, 2015-08-04 at 14:39 +0200, Stefan Roese wrote:
>>> I've used these patches while porting the pxa3xx_nand driver for the
>>> Marvell Armada XP / 38x SoC's to current U-Boot. And have found no
>>> issues so far. So:
>>>
>>> Tested-by: Stefan Roese <sr@denx.de>
>>
>> What are plans for this patch series? Do you plan to send a pull request
>> soon?
>
> The "merge" window (which for U-Boot is really a patch submission window) is
> still open according to the IRC channel topic.  I do plan to submit a pull
> request not too long after it closes.

The merge window has actually been closed by Tom a few days ago:

https://www.mail-archive.com/u-boot at lists.denx.de/msg180049.html

> Meanwhile, Linux's merge window is an actual merge deadline, so most of my
> focus will be there for the moment.

Understood.

>>   Could you perhaps add my patch with the pxa3xx NAND support [1] as
>> well?
>
> It's patch 6/10 -- you want me to pick it independently of the rest?

Yes please. Since it depends on the new Linux NAND driverf sync from you.

Thanks,
Stefan

  reply	other threads:[~2015-08-04 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  6:16 [U-Boot] [PATCH 0/3] nand: Sync with Linux v4.1 Scott Wood
2015-06-27  6:16 ` [U-Boot] [PATCH 1/3] nand: Remove __UBOOT__ ifdefs Scott Wood
2015-06-27  6:16 ` [U-Boot] [PATCH 2/3] mtd: Introduce mtd_block_isreserved() Scott Wood
2015-06-27  6:16 ` [U-Boot] [PATCH 3/3] nand: Sync with Linux v4.1 Scott Wood
2015-07-23  6:51 ` [U-Boot] [PATCH 0/3] " Stefan Roese
2015-08-04 12:39   ` Stefan Roese
2015-08-04 18:26     ` Scott Wood
2015-08-04 23:45       ` Stefan Roese [this message]
2015-08-18 17:55         ` Tom Rini
2015-08-19 21:31           ` Scott Wood

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=55C14EA9.6050008@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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