public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: Song Liu <songliubraving@fb.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [GIT PULL] md-fixes 20210804
Date: Tue, 10 Aug 2021 11:46:59 +0200	[thread overview]
Message-ID: <860cbfb2-8e9b-2965-d7ad-ca7f66c12239@linux.intel.com> (raw)
In-Reply-To: <54C9427A-ADEA-4627-B435-FFF5841E6296@fb.com>

Hi Song,
On 10.08.2021 07:10, Song Liu wrote:
> Sure. md-next branch is for feature development. Patches applied to
> md-next will go through linux-next before merging into upstream.
> md-fixes branch is for bug fixes. Patches applied to md-fixes will
> not go through linux-next.
> 
> Does this answer your question?

Yes, It is clear now.

Thanks,
Mariusz


      reply	other threads:[~2021-08-10  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 21:47 [GIT PULL] md-fixes 20210804 Song Liu
2021-08-04 21:50 ` Jens Axboe
2021-08-09 12:38   ` Tkaczyk, Mariusz
2021-08-10  5:10     ` Song Liu
2021-08-10  9:46       ` Tkaczyk, Mariusz [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=860cbfb2-8e9b-2965-d7ad-ca7f66c12239@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=songliubraving@fb.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