linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
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: Mon, 21 Mar 2022 23:06:40 +0800	[thread overview]
Message-ID: <05a9f84a-dc44-12db-2520-186f1c4450cd@suse.de> (raw)
In-Reply-To: <084cd90c-fada-072e-aade-079b577cf107@suse.de>

On 3/21/22 10:54 PM, Coly Li wrote:
> On 3/21/22 4:14 PM, Mariusz Tkaczyk wrote:
>>
>>>
>> 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?


BTW, just for your information, the patches acked by me are pushed to 
for-jes/20220321 branch of the mdadm-CI tree.


Thanks.


Coly Li


  reply	other threads:[~2022-03-21 15:06 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 [this message]
2022-03-22  7:39         ` Mariusz Tkaczyk
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=05a9f84a-dc44-12db-2520-186f1c4450cd@suse.de \
    --to=colyli@suse.de \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.florczak@linux.intel.com \
    --cc=mariusz.tkaczyk@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 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).