From: Mike Snitzer <snitzer@redhat.com>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools fixes
Date: Fri, 8 May 2009 08:23:32 -0400 [thread overview]
Message-ID: <20090508122332.GA7097@redhat.com> (raw)
In-Reply-To: <4A03B1B4.2080900@ct.jp.nec.com>
On Fri, May 08 2009 at 12:14am -0400,
Kiyoshi Ueda <k-ueda@ct.jp.nec.com> wrote:
> Hi Mike,
>
> On 2009/04/30 5:10 +0900, Mike Snitzer wrote:
> > Christophe,
> >
> > Please feel free to pull in the following changes with:
> > git pull http://people.redhat.com/msnitzer/multipath-tools.git +for-upstream
> >
> > Mike Snitzer (6):
> > multipathd: add error checking to client's process_req
> > avoid NULL pointers in discovery code
> > do not allow relative path names to be added to the pathvec
> > cleanup various MALLOC/REALLOC callers
> > fix small issues in cli_handlers
> > multipathd: restrict /var/run/multipathd.sock permissions further
> >
> > libmultipath/config.c | 2 +-
> > libmultipath/config.h | 1 +
> > libmultipath/dict.c | 8 ++++----
> > libmultipath/discovery.c | 15 ++++++++++++---
> > libmultipath/parser.c | 15 +++++++++------
> > libmultipath/prio.c | 2 +-
> > libmultipath/uevent.c | 2 +-
> > libmultipath/uxsock.c | 2 ++
> > multipathd/cli_handlers.c | 6 +++---
> > multipathd/main.c | 9 +++++++++
> > multipathd/uxclnt.c | 11 ++++++-----
> > 11 files changed, 49 insertions(+), 24 deletions(-)
>
> I think it's nice if you post actual patches, too, in the future.
> Because people can look at your patches easier.
OK, will do.
Regards,
Mike
prev parent reply other threads:[~2009-05-08 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 20:10 multipath-tools fixes Mike Snitzer
2009-04-29 20:55 ` christophe.varoqui
2009-05-08 4:14 ` Kiyoshi Ueda
2009-05-08 12:23 ` Mike Snitzer [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=20090508122332.GA7097@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=k-ueda@ct.jp.nec.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