Linux Device Mapper development
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@strace.io>
To: Martin Wilck <mwilck@suse.com>
Cc: dm-devel@redhat.com
Subject: Re: [dm-devel] [PATCH] 11-dm-mpath.rules: fix warnings reported by udevadm verify
Date: Mon, 22 May 2023 19:43:38 +0300	[thread overview]
Message-ID: <20230522164338.GA7504@altlinux.org> (raw)
In-Reply-To: <d0c9a2ca3ee3e66a151dd17ab9623d0701e2924e.camel@suse.com>

On Mon, May 22, 2023 at 06:11:14PM +0200, Martin Wilck wrote:
[...]
> I see. I'll apply this patch then (and the other one with the missing
> comma, too), but unless you object, I'll add a note to the
> commit message explaining that this for improving readability 
> and coding style compliance. I want to avoid the impression that the
> existing code is technically wrong, which it isn't.

That's fine with me, thanks.


-- 
ldv

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


      reply	other threads:[~2023-05-23  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 22:33 [dm-devel] [PATCH] 11-dm-mpath.rules: fix warnings reported by udevadm verify Dmitry V. Levin
2023-05-22 10:19 ` Martin Wilck
2023-05-22 10:49   ` Dmitry V. Levin
2023-05-22 16:11     ` Martin Wilck
2023-05-22 16:43       ` Dmitry V. Levin [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=20230522164338.GA7504@altlinux.org \
    --to=ldv@strace.io \
    --cc=dm-devel@redhat.com \
    --cc=mwilck@suse.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