All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Coly Li <colyli@suse.de>
Cc: Lukasz Florczak <lukasz.florczak@linux.intel.com>,
	jes@trained-monkey.org, pmenzel@molgen.mpg.de,
	linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/4] mdadm: Respect config file location in man
Date: Tue, 22 Mar 2022 08:39:26 +0100	[thread overview]
Message-ID: <20220322083926.00001f04@linux.intel.com> (raw)
In-Reply-To: <084cd90c-fada-072e-aade-079b577cf107@suse.de>

On Mon, 21 Mar 2022 22:54:41 +0800
Coly Li <colyli@suse.de> wrote:

> On 3/21/22 4:14 PM, Mariusz Tkaczyk wrote:
> > On Sun, 20 Mar 2022 17:54:56 +0800
> > Coly Li <colyli@suse.de> wrote:
> >  
> >> On 3/18/22 4:26 PM, Lukasz Florczak wrote:  
> >>> Default config file location could differ depending on OS (e.g.
> >>> Debian family). This patch takes default config file into
> >>> consideration when creating mdadm.man file as well as
> >>> mdadm.conf.man.
> >>>
> >>> Rename mdadm.conf.5 to mdadm.conf.5.in. Now mdadm.conf.5 is
> >>> generated automatically.
> >>>
> >>> Signed-off-by: Lukasz Florczak <lukasz.florczak@linux.intel.com>  
> >>
> >> I test and verify the change under openSUSE.
> >>
> >>
> >> Acked-by: Coly Li <colyli@suse.de>
> >>
> >>  
> > Hi Coly,
> > Could you please merge it to your master/for-jes branch then?  
> 
> Sure, I will do it.
> 
> Just to confirm, for this situation, do you want me to add the patch 
> directly to for-jes branch with my Acked-by: tag, or you will post 
> another version with the Acked-by: tag?
> 
Please do. Asking author to post another version will bring unnecessary
harm. Just take it and add your tag.

> 
> > We have additional CI at Intel, based on our internal IMSM scope.
> > I would like to switch it to your master/for-jes branch. Also I
> > want to base future development on your tree.  
> 
> 
> Copied.

I can see that you named the branch with the date. Do you plan to
create more for-jes branches?
https://git.kernel.org/pub/scm/linux/kernel/git/colyli/mdadm.git/log/?h=for-jes/20220321

> 
> 
> > Could you also elaborate more, what kind of testing are you doing?  
> 
> 
> Currently I only compile the patches, and create simple md raid1 
> with/without container, and show them with mdadm -D and -E.
> 
> For the manual modification, it is checked by myself. I compile the
> man page, and check the CONFFILE and CONFFILE2 replacement in man
> page is correct on openSUSE. Then I run checkpatch.pl from Linux
> kernel with --codespell to check the patch style and basic spelling.
> And finally read the changed content of the man page.
> 
> 
> > I think that is a good moment to give new life to mdadm test suite,
> > if you are using it.  
> 
> 
> I am thinking of create another separate git repo, to store all the 
> testing scripts, and run them on the mdadm-CI tree.

Make sense.

Thanks,
Mariusz


  parent reply	other threads:[~2022-03-22  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  8:26 [PATCH v2 0/4] Manual improvements Lukasz Florczak
2022-03-18  8:26 ` [PATCH 1/4] mdadm: Respect config file location in man Lukasz Florczak
2022-03-20  9:54   ` Coly Li
2022-03-21  8:14     ` Mariusz Tkaczyk
2022-03-21 14:54       ` Coly Li
2022-03-21 15:06         ` Coly Li
2022-03-22  7:39         ` Mariusz Tkaczyk [this message]
2022-04-05  1:12   ` Jes Sorensen
2022-03-18  8:26 ` [PATCH 2/4] mdadm: Update ReadMe Lukasz Florczak
2022-03-20 14:05   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen
2022-03-18  8:26 ` [PATCH 3/4] mdadm: Update config man regarding default files and multi-keyword behavior Lukasz Florczak
2022-03-20 14:54   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen
2022-03-18  8:26 ` [PATCH 4/4] mdadm: Update config manual Lukasz Florczak
2022-03-20 14:54   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen

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=20220322083926.00001f04@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=colyli@suse.de \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.florczak@linux.intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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.