From: Petr Vorel <petr.vorel@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: dm-devel@redhat.com, Baruch Even <baruch@ev-en.org>
Subject: Re: [PATCH 1/1] kpartx: Use __kernel_daddr_t for solaris_x86_slice.s_start
Date: Tue, 8 Oct 2019 10:18:32 +0200 [thread overview]
Message-ID: <20191008081831.GA29132@dell5510> (raw)
In-Reply-To: <20191007165732.GA4805@infradead.org>
Hi Christoph,
> On Wed, Oct 02, 2019 at 08:05:09AM +0200, Petr Vorel wrote:
> > I tried to search in [1], with not much success, I don't know the original name
> > of the struct and struct members are quite similar. Do you have a tip, where it
> > could be or would you dare to search?
> No, I don't know Solaris very well.
> > Christophe already merged my patch as
> > 129e6fe6 ("kpartx: Use __kernel_daddr_t for solaris_x86_slice.s_start")
> > But, according to your comments it looks to me better to use the exact structure
> > kernel uses. So, if we don't find anything, I'd be for using kernel struct.
> Thanks, that would be great.
I've sent a patch, as RFC, Cc also Baruch Even, the gpart maintainer.
I wonder, if there is anybody actually using this code nowadays.
Kind regards,
Petr
next prev parent reply other threads:[~2019-10-08 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 21:35 [PATCH 1/1] kpartx: Use __kernel_daddr_t for solaris_x86_slice.s_start Petr Vorel
2019-07-09 2:47 ` Christoph Hellwig
2019-07-09 8:02 ` Petr Vorel
2019-07-09 13:34 ` Christoph Hellwig
2019-10-02 6:05 ` Petr Vorel
2019-10-07 16:57 ` Christoph Hellwig
2019-10-08 8:18 ` Petr Vorel [this message]
2019-10-12 9:01 ` Baruch Even
2019-10-12 19:08 ` Petr Vorel
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=20191008081831.GA29132@dell5510 \
--to=petr.vorel@gmail.com \
--cc=baruch@ev-en.org \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.