All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	kmpark@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: 2.6.32 -mm merge plans
Date: Wed, 16 Sep 2009 10:09:55 +0300	[thread overview]
Message-ID: <4AB08F43.3080603@gmail.com> (raw)
In-Reply-To: <20090916000357.GD23923@linux-sh.org>

On 09/16/2009 03:03 AM, Paul Mundt wrote:
> On Tue, Sep 15, 2009 at 04:15:35PM -0700, Andrew Morton wrote:
>> mtd-make-onenand-genericc-more-generic.patch
>> mtd-nand-add-page-parameter-to-all-read_page-read_page_raw-apis.patch
>> mtd-nand-add-new-ecc-mode-ecc_hw_oob_first.patch
>> mtd-nand-davinci-add-4-bit-ecc-support-for-large-page-nand-chips.patch
>> mtd-nand-davinci-add-4-bit-ecc-support-for-large-page-nand-chips-update.patch
>> mtd-jffs2-fix-read-buffer-overflow.patch
>> mtd-prevent-a-read-from-eraseregions.patch
>> mtd-prevent-a-read-from-regions.patch
>> mtd-jedec_probe-fix-nec-upd29f064115-detection.patch
>> mtdpart-memory-accessor-interface-for-mtd-layer.patch
>>
>>    ->  dwmw2
>>
> Regarding mtd-make-onenand-genericc-more-generic.patch, I'm not really
> sure what happened. To recap:
>
> It was posted to the mtd list here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-August/026805.html
>
> Kyungmin objected to the driver name change here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-August/026807.html
>
> I pointed out that the rough rationale for the name change here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-August/026808.html
>
> and offered to redo the patch keeping the old name if Kyungmin felt the
> rationale wasn't valid, but received no reply. Subsequently, Artem
> mentioned that he had merged it in to his l2-mtd-2.6.git tree here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-August/026866.html
>
> which subsequently seems to not actually have happened.

Well, I did put my patch to my l2-mtd-2.6.git tree:

http://git.infradead.org/users/dedekind/l2-mtd-2.6.git/commit/6e6e7d0e163148c620b4807b1ffac973f9805f20

I just put it to the dunno branch which means "I did not review this".
The master branch contains the stuff I did review.

And the idea was that dwmw2 would then take a look at all these patches
and merge them. He did merge the stuff from the master branch, but did not
merge the stuff from the dunno branch (yet).

> This is a pretty trivial patch, and I don't mind respinning it in
> whatever form folks are content with. I had assumed given the mention
> that it had been merged in to the l2 tree that the rationale was
> sufficient for merging.

I know it is frustrating when maintainers ignore patches, we feel this pain
with ARM patches, for example. It is unpleasant to re-send patches 4 times,
and get zero response, not even "I have not time now" one. On the other hand,
I understand maintainers who are busy with other things.

So I just try to help by collecting people's stuff, review _some_ of it, but
I do not merge this upstream.

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

  parent reply	other threads:[~2009-09-16  7:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 23:15 2.6.32 -mm merge plans Andrew Morton
2009-09-15 23:15 ` Andrew Morton
2009-09-16  0:03 ` Paul Mundt
2009-09-16  0:03   ` Paul Mundt
2009-09-16  0:18   ` Andrew Morton
2009-09-16  0:18     ` Andrew Morton
2009-09-16  3:51     ` Mike Frysinger
2009-09-16  3:51       ` Mike Frysinger
2009-09-16  4:15       ` Andrew Morton
2009-09-16  4:15         ` Andrew Morton
2009-09-16  4:17         ` Mike Frysinger
2009-09-16  4:17           ` Mike Frysinger
2009-09-16  7:21       ` Artem Bityutskiy
2009-09-16  7:21         ` Artem Bityutskiy
2009-09-16  7:09   ` Artem Bityutskiy [this message]
2009-09-16  7:36     ` Artem Bityutskiy
2009-09-16  3:46 ` Dmitry Torokhov
2009-09-16  3:46   ` Dmitry Torokhov
2009-09-16  4:14   ` Andrew Morton
2009-09-16  4:14     ` Andrew Morton
2009-09-16  8:33     ` David Härdeman
2009-09-16  8:33       ` David Härdeman
2009-09-16 15:00     ` Bjorn Helgaas
2009-09-16 15:00       ` Bjorn Helgaas
2009-09-16 20:00       ` Andrew Morton
2009-09-16 20:00         ` Andrew Morton
2009-09-16  7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16  7:37   ` Balbir Singh
2009-09-16  7:51   ` Daisuke Nishimura
2009-09-16  7:51     ` Daisuke Nishimura
2009-09-16  7:58   ` KAMEZAWA Hiroyuki
2009-09-16  7:58     ` KAMEZAWA Hiroyuki
2009-09-16  8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16  8:45   ` Pavel Machek
2009-09-16  9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-16  9:42   ` Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:15   ` Oleg Nesterov
2009-09-17 20:38   ` Andrew Morton
2009-09-17 20:38     ` Andrew Morton
2009-09-17 21:08     ` Oleg Nesterov
2009-09-17 21:08       ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:32   ` Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 20:46   ` Oleg Nesterov
2009-09-17 21:56   ` Roland McGrath
2009-09-17 21:56     ` Roland McGrath

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=4AB08F43.3080603@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=kmpark@infradead.org \
    --cc=lethal@linux-sh.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.