Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Rosen Penev <rosenp@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: Eliminate remaining uses of strerror(errno)
Date: Thu, 13 Sep 2018 11:50:28 +0200	[thread overview]
Message-ID: <20180913095028.GR2154@twin.jikos.cz> (raw)
In-Reply-To: <8523769a-dc37-81aa-138a-4702a8c2d009@suse.com>

On Thu, Sep 13, 2018 at 09:17:17AM +0300, Nikolay Borisov wrote:
> 
> 
> On 13.09.2018 03:52, Rosen Penev wrote:
> > %m allows a smaller filesize. Useful on embedded systems.
> > 
> > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > ---
> >  build/Documentation/Makefile |  142 +++++
> >  build/Makefile.inc           |   42 ++
> >  build/config.h               |  139 +++++
> >  build/config.log             |  822 ++++++++++++++++++++++++++
> >  build/config.status          | 1059 ++++++++++++++++++++++++++++++++++
> >  build/version.h              |   14 +
> >  cmds-qgroup.c                |    3 +-
> >  messages.h                   |    4 +-
> >  mkfs/rootdir.c               |   47 +-
> >  qgroup.c                     |    3 +-
> >  10 files changed, 2243 insertions(+), 32 deletions(-)
> >  create mode 100644 build/Documentation/Makefile
> >  create mode 100644 build/Makefile.inc
> >  create mode 100644 build/config.h
> >  create mode 100644 build/config.log
> >  create mode 100755 build/config.status
> >  create mode 100644 build/version.h
> 
> You clearly need to resend with changes only to  the *.[ch] files

No need to resend, the .[ch] changes look good, I'll drop the rest.

      reply	other threads:[~2018-09-13 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  0:52 [PATCH] btrfs-progs: Eliminate remaining uses of strerror(errno) Rosen Penev
2018-09-13  6:17 ` Nikolay Borisov
2018-09-13  9:50   ` David Sterba [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=20180913095028.GR2154@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=rosenp@gmail.com \
    /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