From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>, Petr Uzel <petr.uzel@suse.cz>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: [PATCH 09/10] fdisk: API: fix fdisk_label_create
Date: Sun, 22 Jul 2012 19:05:45 +0200 [thread overview]
Message-ID: <1342976745.2863.19.camel@offbook> (raw)
From: Davidlohr Bueso <dave@gnu.org>
It wasn't actually calling create_label(), silly me!
Signed-off-by: Davidlohr Bueso <dave@gnu.org>
---
fdisks/utils.c | 12 +++++++-----
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/fdisks/utils.c b/fdisks/utils.c
index 62cd6aa..510d641 100644
--- a/fdisks/utils.c
+++ b/fdisks/utils.c
@@ -143,11 +143,13 @@ int fdisk_label_create(struct fdisk_context *cxt, const char *name)
#else
errcode = fdisk_label_change(cxt, "dos");
#endif
- if (errcode)
- goto done;
- }
-
- errcode = fdisk_label_change(cxt, name);
+ } else
+ errcode = fdisk_label_change(cxt, name);
+
+ if (errcode)
+ goto done;
+
+ errcode = cxt->label->create_label(cxt);
done:
return errcode;
}
--
1.7.4.1
next reply other threads:[~2012-07-22 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 17:05 Davidlohr Bueso [this message]
2012-07-24 11:40 ` [PATCH 09/10] fdisk: API: fix fdisk_label_create Karel Zak
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=1342976745.2863.19.camel@offbook \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=petr.uzel@suse.cz \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).