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 v2 0/4] MTD & UBI fixes
Date: Wed, 11 Sep 2013 07:48:03 +0200	[thread overview]
Message-ID: <52300413.40206@denx.de> (raw)
In-Reply-To: <1378844668.12204.341.camel@snotra.buserror.net>

On 10.09.2013 22:24, Scott Wood wrote:
> On Sat, 2013-09-07 at 14:11 +0200, Stefan Roese wrote:
>> On 04.09.2013 16:16, Paul Burton wrote:
>>> This patchset corrects a few issues I've had whilst using UBI with U-boot.
>>>
>>> The first 3 are bug fixes, the 4th is an addition I needed in order to write a
>>> large root filesystem into my NAND device.
>>>
>>> Changes since v1:
>>>   - Fixed style issues in "cmd_ubi: add write.part command..." as per
>>>     Stefan Roese's comments.
>>>   - Expanded upon the condition patch 1 fixes in response to the
>>>     queries from Stefan, see the commit message for further detail.
>>>   - Added patch 3 "cmd_ubi: use int64_t volume size for 'ubi create'"
>>>     which it seems appropriate to include in this series.
>>>
>>> Paul Burton (4):
>>>   mtd: driver _read() returns max_bitflips; mtd_read() returns -EUCLEAN
>>>   cmd_mtdparts: use 64 bits for flash size, partition size & offset
>>>   cmd_ubi: use int64_t volume size for 'ubi create'
>>>   cmd_ubi: add write.part command, to write a volume in multiple parts
>>
>> All 4 patches:
>>
>> Acked-by: Stefan Roese <sr@denx.de>
>>
>> Scott, these patches are assigned to you in patchwork. If you are okay
>> with the NAND side (and everything else), then please feel free to push
>> all 4 patches via your repository.
> 
> Patch 1 looks OK to me (at least to the extent that it's just bringing
> code over from Linux).  Patch 2 also looks straightforward.
> 
> Kyungmin is the UBI maintainer -- the last two patches need his ack.

Yes, Kyungmin is the "official" UBI maintainer. But I have been taking
care of all UBI (and UBIFS) related patches in the last years
(collecting and pushing them upstream in the u-boot-ubi git repository).

Kyungmin, how should we handle this in the future. Would you like to
handle the UBI (and UBIFS) patches yourself? Please let us know how to
proceed.

Thanks,
Stefan

  reply	other threads:[~2013-09-11  5:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 14:16 [U-Boot] [PATCH v2 0/4] MTD & UBI fixes Paul Burton
2013-09-04 14:16 ` [U-Boot] [PATCH v2 1/4] mtd: driver _read() returns max_bitflips; mtd_read() returns -EUCLEAN Paul Burton
2013-09-04 14:16 ` [U-Boot] [PATCH 2/4] cmd_mtdparts: use 64 bits for flash size, partition size & offset Paul Burton
2013-10-15 17:27   ` York Sun
2013-09-04 14:16 ` [U-Boot] [PATCH 3/4] cmd_ubi: use int64_t volume size for 'ubi create' Paul Burton
2013-09-04 14:16 ` [U-Boot] [PATCH v2 4/4] cmd_ubi: add write.part command, to write a volume in multiple parts Paul Burton
2013-09-07 12:11 ` [U-Boot] [PATCH v2 0/4] MTD & UBI fixes Stefan Roese
2013-09-10 20:24   ` Scott Wood
2013-09-11  5:48     ` Stefan Roese [this message]
2013-09-12  0:55       ` Scott Wood
2013-09-12  5:55         ` Stefan Roese

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=52300413.40206@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