public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/4] fs: export fs_close()
Date: Mon, 7 Oct 2019 11:08:06 +0900	[thread overview]
Message-ID: <20191007020805.GS18778@linaro.org> (raw)
In-Reply-To: <03a5e2c9-5ed6-4856-e470-3b819f4c40a8@gmx.de>

On Fri, Oct 04, 2019 at 08:53:00PM +0200, Heinrich Schuchardt wrote:
> On 10/4/19 5:05 AM, AKASHI Takahiro wrote:
> > This function is always paired with either fs_set_blk_desc() or
> > fs_set_blk_desc_with_part(). So just export it.
> >
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > ---
> >  fs/fs.c      | 2 +-
> >  include/fs.h | 7 +++++++
> >  2 files changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/fs.c b/fs/fs.c
> > index d8a4ced4698e..64ba25fea8bf 100644
> > --- a/fs/fs.c
> > +++ b/fs/fs.c
> > @@ -389,7 +389,7 @@ int fs_set_blk_dev_with_part(struct blk_desc *desc, int part)
> >  	return -1;
> >  }
> >
> > -static void fs_close(void)
> > +void fs_close(void)
> >  {
> >  	struct fstype_info *info = fs_get_info(fs_type);
> >
> > diff --git a/include/fs.h b/include/fs.h
> > index 7601b0343bcd..5a1244d57fd2 100644
> > --- a/include/fs.h
> > +++ b/include/fs.h
> > @@ -37,6 +37,13 @@ int fs_set_blk_dev(const char *ifname, const char *dev_part_str, int fstype);
> >   */
> >  int fs_set_blk_dev_with_part(struct blk_desc *desc, int part);
> >
> > +/**
> > + * fs_close() - Unset current block device and partition
> > + *
> > + * Should be paired with either fs_set_blk_dev() or fs_set_dev_with_part()
> 
> This "paired" implies that one should call one of the name functions
> afterwards which may not be necessary. I would suggest:
> 
> "fs_close() closes the connection to a file system which opened with
> either fs_set_blk_dev() or fs_set_dev_with_part(). Many file functions
> implicitly call fs_close(), e.g. fs_closedir(), fs_exist(), fs_ln(),
> fs_ls(), fs_mkdir(), fs_read(), fs_size(), fs_write(), fs_unlink()."

Okay.

-Takahiro Akashi


> Best regards
> 
> Heinrich Schuchardt
> 
> > + */
> > +void fs_close(void);
> > +
> >  /**
> >   * fs_get_type_name() - Get type of current filesystem
> >   *
> >
> 

  reply	other threads:[~2019-10-07  2:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  3:05 [U-Boot] [PATCH v3 0/4] efi_loader: disk: install FILE_SYSTEM_PROTOCOL to whole disk AKASHI Takahiro
2019-10-04  3:05 ` [U-Boot] [PATCH v3 1/4] fs: export fs_close() AKASHI Takahiro
2019-10-04 18:53   ` Heinrich Schuchardt
2019-10-07  2:08     ` AKASHI Takahiro [this message]
2019-10-04  3:05 ` [U-Boot] [PATCH v3 2/4] fs: add fs_get_type() for current filesystem type AKASHI Takahiro
2019-10-04 19:04   ` Heinrich Schuchardt
2019-10-07  2:13     ` AKASHI Takahiro
2019-10-04  3:05 ` [U-Boot] [PATCH v3 3/4] efi_loader: disk: install FILE_SYSTEM_PROTOCOL only if available AKASHI Takahiro
2019-10-04 19:13   ` Heinrich Schuchardt
2019-10-07  2:15     ` AKASHI Takahiro
2019-10-04  3:05 ` [U-Boot] [PATCH v3 4/4] efi_loader: disk: install file system protocol to a whole disk AKASHI Takahiro
2019-10-04 19:15   ` Heinrich Schuchardt
2019-10-07  2:27     ` AKASHI Takahiro

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=20191007020805.GS18778@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --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