From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Artem Bityutskiy <dedekind1@gmail.com>,
Richard Weinberger <richard@nod.at>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] UBI: provide helpers to allocate and free aeb elements
Date: Fri, 26 Aug 2016 11:02:09 +0200 [thread overview]
Message-ID: <20160826110209.2d74170b@bbrezillon> (raw)
In-Reply-To: <1471937574-8045-8-git-send-email-boris.brezillon@free-electrons.com>
On Tue, 23 Aug 2016 09:32:54 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> This not only hides the aeb allocation internals (which is always good in
> case we ever want to change the allocation system), but also helps us
> factorize the initialization of some common fields (ec and pnum).
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> drivers/mtd/ubi/attach.c | 68 ++++++++++++++++++++++++++++++++++-------------
> drivers/mtd/ubi/fastmap.c | 28 +++++++------------
> drivers/mtd/ubi/ubi.h | 3 +++
> drivers/mtd/ubi/vtbl.c | 4 +--
> 4 files changed, 65 insertions(+), 38 deletions(-)
>
> diff --git a/drivers/mtd/ubi/attach.c b/drivers/mtd/ubi/attach.c
> index be83c17d742b..ba88ff582f1a 100644
> --- a/drivers/mtd/ubi/attach.c
> +++ b/drivers/mtd/ubi/attach.c
> @@ -182,6 +182,46 @@ static struct ubi_ainf_volume *ubi_find_or_add_av(struct ubi_attach_info *ai,
> }
>
> /**
> + * ubi_alloc_aeb - allocate an aeb element
> + * @ai: attaching information
> + * @aeb: the element to free
The kernel doc is wrong. I'll fix that in v2.
> + *
> + * Allocate an aeb object and initialize the pnum and ec information.
> + * vol_id and lnum are set to UBI_UNKNOWN, and the other fields are
> + * initialized to zero.
> + * Note that the element is not added in any list or RB tree.
> + */
> +struct ubi_ainf_peb *ubi_alloc_aeb(struct ubi_attach_info *ai, int pnum,
> + int ec)
> +{
> + struct ubi_ainf_peb *aeb;
> +
> + aeb = kmem_cache_zalloc(ai->aeb_slab_cache, GFP_KERNEL);
> + if (!aeb)
> + return NULL;
> +
> + aeb->pnum = pnum;
> + aeb->ec = ec;
> + aeb->vol_id = UBI_UNKNOWN;
> + aeb->lnum = UBI_UNKNOWN;
> +
> + return aeb;
> +}
> +
prev parent reply other threads:[~2016-08-26 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:32 [PATCH 0/7] UBI: various cleanup/fixes Boris Brezillon
2016-08-23 7:32 ` [PATCH 1/7] UBI: fastmap: use ubi_find_volume() instead of open coding it Boris Brezillon
2016-08-23 7:32 ` [PATCH 2/7] UBI: fastmap: avoid multiple be32_to_cpu() when unneccesary Boris Brezillon
2016-08-23 7:32 ` [PATCH 3/7] UBI: fastmap: scrub PEB when bitflips are detected in a free PEB EC header Boris Brezillon
2016-08-23 7:32 ` [PATCH 4/7] UBI: factorize code used to manipulate volumes at attach time Boris Brezillon
2016-08-23 7:32 ` [PATCH 5/7] UBI: factorize destroy_av() and ubi_remove_av() code Boris Brezillon
2016-08-23 7:32 ` [PATCH 6/7] UBI: fastmap: use ubi_rb_for_each_entry() in unmap_peb() Boris Brezillon
2016-08-23 7:32 ` [PATCH 7/7] UBI: provide helpers to allocate and free aeb elements Boris Brezillon
2016-08-26 9:02 ` Boris Brezillon [this message]
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=20160826110209.2d74170b@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).