From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Richard Laager <rlaager@wiktel.com>
Cc: grub-devel@gnu.org, Zachary Bedell <pendorbound@gmail.com>
Subject: Re: [Patch] Robustly search for ZFS labels & uberblocks
Date: Fri, 03 Feb 2012 10:52:16 +0100 [thread overview]
Message-ID: <4F2BAE50.5060809@gmail.com> (raw)
In-Reply-To: <1327999542.3471.20.camel@watermelon.coderich.net>
On 31.01.2012 09:45, Richard Laager wrote:
> Attached is a stack of trivial patches that apply*on top of* your
> zfs.diff from 2012-01-29. They each deal with one logical change and
> should be very easy to review.
>
> After your original patch and this stack have been dealt with, I'll
> submit an updated patch for native ZFS on Linux support, which is much
> shorter than before.
>
> --
> Richard
>
> zfs-on-linux-rlaager0.patch
>
>
> Eliminate stray trailing spaces.
We don't do it manually, just from time to time run it automatically on
whole codebase.
>
> zfs-on-linux-rlaager1.patch
>
>
> Change device to devices in find_root_devices_from_libzfs
>
>
>
committed
> zfs-on-linux-rlaager2.patch
>
>
> Change strlen to sizeof
It doesn't matter since GCC changes strlen of const string to just a
const. But applied for conformity with the rest of codebase
>
> zfs-on-linux-rlaager3.patch
>
>
> Avoid crashing when canonicalize_file_name() fails
>
> I could reproduce this with: grub-probe /dev/sda1
>
>
>
Committed
> zfs-on-linux-rlaager4.patch
>
>
> Drop an unused variable.
>
>
>
committed.
> zfs-on-linux-rlaager5.patch
>
>
> Add braces around and indent the `zpool status` parsing loop
Not needed. And we don't put a braces which are not needed.
>
> zfs-on-linux-rlaager6.patch
>
>
> Handle pool names with trailing spaces
What about the ones with spaces in the middle? It feels like the logic
is broken elsewhere and using strncmp is just a workaround which works
only for one particular case
> zfs-on-linux-rlaager7.patch
>
>
> Handle all raidz types in `zpool status` output
>
>
Committed.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-02-03 9:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 18:45 [Patch] Robustly search for ZFS labels & uberblocks Zachary Bedell
2011-09-28 21:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-19 11:36 ` Richard Laager
2012-01-22 14:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-22 20:31 ` Richard Laager
2012-01-24 7:12 ` Richard Laager
2012-01-27 19:04 ` Zachary Bedell
2012-01-27 22:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 2:50 ` Richard Laager
2012-01-28 12:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 16:50 ` Richard Laager
2012-01-28 17:06 ` Darik Horn
2012-01-28 17:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-28 18:33 ` Richard Laager
2012-01-28 19:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-29 22:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-31 8:45 ` Richard Laager
2012-02-02 11:13 ` Richard Laager
2012-02-03 10:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-03 9:52 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-03 11:20 ` Richard Laager
2012-01-28 18:40 ` Darik Horn
2012-01-28 19:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-01-30 1:22 ` Richard Laager
2012-01-30 1:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-03 14:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F2BAE50.5060809@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=pendorbound@gmail.com \
--cc=rlaager@wiktel.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;
as well as URLs for NNTP newsgroup(s).