From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] UBI: Fastmap: Ensure that all fastmap work is done upon WL shutdown
Date: Fri, 28 Nov 2014 10:53:16 +0100 [thread overview]
Message-ID: <5478460C.10000@nod.at> (raw)
In-Reply-To: <1417106877.5858.133.camel@sauron.fi.intel.com>
Am 27.11.2014 um 17:47 schrieb Artem Bityutskiy:
> On Thu, 2014-11-27 at 17:35 +0100, Richard Weinberger wrote:
>> Am 27.11.2014 um 17:29 schrieb Artem Bityutskiy:
>>> On Thu, 2014-11-27 at 17:08 +0100, Richard Weinberger wrote:
>>>>> Obviously, there is some misunderstanding. This looks like lack of
>>>>> separation and misuse of layering. I am missing explanations why I am
>>>>> wrong...
>>>>
>>>> So you want me to use the UBI WL background thread for the scheduled fastmap work?
>>>
>>> No. It is more like either use it or do not use it.
>>
>> Sorry, I don't understand.
>> What do you want to do to?
>
> Just keep the code structured. I am just asking questions and trying to
> to analyze your patches. If at some point I would like you to do
> something specific, I clearly state this. In this case I was complaining
> about fastmap specifics in an unrelated file, so basically the wish is
> to have it go away. How exactly - not specified, up to you :-) Or, this
> means just telling me why it is this way, justify.
>
> When I was working with this code, I did give people specific
> suggestions, line-by-line. Now I am more doing more of a sanity check,
> looking after the bigger picture.
>
> I understand that this is not a picture of an ideal maintainer, and I am
> not anymore an ideal maintainer for this stuff (I think I used to,
> though), simply because of lack of time. Doing the best effort job now.
This is perfectly fine. I'm trying hard to keep your job as easy as possible.
>>>> I didn't do it that way because you said more than once that fastmap is fastmap and
>>>> WL is WL. Therefore I've separated it.
>>>
>>> And "separated" meaning adding this code to wl.c?
>>>
>>> +#ifdef CONFIG_MTD_UBI_FASTMAP
>>> + flush_work(&ubi->fm_work);
>>> +#endif
>>>
>>> Could it be separated some more then?
>>>
>>
>> Of course, commit "UBI: Move fastmap specific functions out of wl.c" does.
>
> I did not see it in this series. So you could tell this earlier, not
> after 2 e-mail exchanges. Do not assume I remember the details of our
> previous discussion. Assume I forgot everything :-)
You did not see it in that series because you asked me to split it.
The massive clean stuff comes after the fixes.
This is the branch where I keep the whole series.
https://git.kernel.org/cgit/linux/kernel/git/rw/misc.git/log/?h=fastmap_upgrade2
Right now you've seen 6 out of 40 patches.
Maybe I'll change a few commits before submitting them.
I have some new ideas for more cleanups. :)
>> But this commit is *bugfix* commit.
>
> I thought adding an close function to fastmap.c is a simple task.
As I said, later in the series I clean up a lot.
Thanks,
//richard
next prev parent reply other threads:[~2014-11-28 9:53 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 13:20 Fastmap update v2 (pile 1) Richard Weinberger
2014-11-24 13:20 ` [PATCH 1/6] UBI: Fastmap: Care about the protection queue Richard Weinberger
2014-11-27 14:54 ` Artem Bityutskiy
2015-01-09 21:23 ` Ezequiel Garcia
2015-01-09 21:31 ` Richard Weinberger
2015-01-09 21:34 ` Ezequiel Garcia
2014-11-24 13:20 ` [PATCH 2/6] UBI: Fastmap: Ensure that only one fastmap work is scheduled Richard Weinberger
2014-11-27 15:27 ` Artem Bityutskiy
2014-11-27 16:13 ` Richard Weinberger
2014-11-27 16:35 ` Artem Bityutskiy
2014-11-27 16:39 ` Richard Weinberger
2014-11-27 16:49 ` Artem Bityutskiy
2014-12-04 16:14 ` Tanya Brokhman
2014-12-17 13:51 ` Guido Martínez
2014-11-24 13:20 ` [PATCH 3/6] UBI: Fastmap: Ensure that all fastmap work is done upon WL shutdown Richard Weinberger
2014-11-27 15:38 ` Artem Bityutskiy
2014-11-27 16:08 ` Richard Weinberger
2014-11-27 16:29 ` Artem Bityutskiy
2014-11-27 16:35 ` Richard Weinberger
2014-11-27 16:47 ` Artem Bityutskiy
2014-11-28 9:53 ` Richard Weinberger [this message]
2014-12-04 16:44 ` Tanya Brokhman
2014-12-04 17:21 ` Richard Weinberger
2014-12-17 14:26 ` Guido Martínez
2015-01-09 21:32 ` Ezequiel Garcia
2015-01-09 21:37 ` Richard Weinberger
2015-01-09 21:39 ` Ezequiel Garcia
2014-11-24 13:20 ` [PATCH 4/6] UBI: Fastmap: Fix races in ubi_wl_get_peb() Richard Weinberger
2014-12-05 13:09 ` Tanya Brokhman
2014-12-05 13:20 ` Richard Weinberger
2014-12-05 16:54 ` Tanya Brokhman
2014-12-05 21:08 ` Richard Weinberger
2014-12-07 7:36 ` Tanya Brokhman
2014-12-07 9:45 ` Richard Weinberger
2014-11-24 13:20 ` [PATCH 5/6] UBI: Split __wl_get_peb() Richard Weinberger
2014-12-05 17:41 ` Tanya Brokhman
2014-12-05 21:02 ` Richard Weinberger
2014-12-17 15:03 ` Guido Martínez
2014-11-24 13:20 ` [PATCH 6/6] UBI: Fastmap: Make ubi_refill_pools() fair Richard Weinberger
2014-12-05 17:55 ` Tanya Brokhman
2014-12-05 20:56 ` Richard Weinberger
2014-12-07 7:55 ` Tanya Brokhman
2014-12-07 9:49 ` Richard Weinberger
2014-12-17 15:48 ` Guido Martínez
2014-11-27 14:53 ` Fastmap update v2 (pile 1) Artem Bityutskiy
2014-11-27 14:59 ` Richard Weinberger
2014-12-10 8:21 ` Richard Weinberger
2015-01-05 10:37 ` Richard Weinberger
2015-01-09 21:38 ` Ezequiel Garcia
2015-01-09 21:55 ` Richard Weinberger
2015-01-09 22:09 ` Ezequiel Garcia
2015-01-09 22:20 ` Richard Weinberger
2015-03-29 10:46 ` Richard Weinberger
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=5478460C.10000@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome