public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [GIT PULL] md-fixes 20210804
Date: Tue, 10 Aug 2021 05:10:55 +0000	[thread overview]
Message-ID: <54C9427A-ADEA-4627-B435-FFF5841E6296@fb.com> (raw)
In-Reply-To: <66c72f4f-7fa0-7491-e4ea-8d8a82483aaa@linux.intel.com>

Hi Mariusz,

> On Aug 9, 2021, at 5:38 AM, Tkaczyk, Mariusz <mariusz.tkaczyk@linux.intel.com> wrote:
> 
> On 04.08.2021 23:50, Jens Axboe wrote:
>> On 8/4/21 3:47 PM, Song Liu wrote:
>>> Hi Jens,
>>> 
>>> Please consider pulling the following fix on top of your for-5.14/block> branch.
> 
> Hi Song,
> 
> Could you describe idea behind of "md-next" and "md-fixes" branches?
> I'm asking because we are running regression on "md-next", but since
> development has been divided into two separate branches I probably
> need to change current approach.

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? 

Thanks,
Song

  reply	other threads:[~2021-08-10  5:11 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 [this message]
2021-08-10  9:46       ` Tkaczyk, Mariusz

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=54C9427A-ADEA-4627-B435-FFF5841E6296@fb.com \
    --to=songliubraving@fb.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@linux.intel.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