[GIT PULL] md-fixes 20210804

5 messages, 3 authors, 2021-08-10 · open the first message on its own page

[GIT PULL] md-fixes 20210804

From: Song Liu <hidden>
Date: 2021-08-04 21:47:11

Hi Jens, 

Please consider pulling the following fix on top of your for-5.14/block
branch. 

Thanks,
Song



The following changes since commit 2705dfb2094777e405e065105e307074af8965c1:

  block: fix discard request merge (2021-06-29 07:41:08 -0600)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes

for you to fetch changes up to 5ba03936c05584b6f6f79be5ebe7e5036c1dd252:

  md/raid10: properly indicate failure when ending a failed write request (2021-07-23 10:14:07 -0700)

----------------------------------------------------------------
Wei Shuyu (1):
      md/raid10: properly indicate failure when ending a failed write request

 drivers/md/raid1.c  | 2 --
 drivers/md/raid10.c | 4 ++--
 2 files changed, 2 insertions(+), 4 deletions(-)

Re: [GIT PULL] md-fixes 20210804

From: Jens Axboe <axboe@kernel.dk>
Date: 2021-08-04 21:50:41

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. 
Pulled, thanks.

-- 
Jens Axboe

Re: [GIT PULL] md-fixes 20210804

From: Tkaczyk, Mariusz <hidden>
Date: 2021-08-09 12:39:20

On 04.08.2021 23:50, Jens Axboe wrote:
On 8/4/21 3:47 PM, Song Liu wrote:
quoted
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.

Thanks,
Mariusz

Re: [GIT PULL] md-fixes 20210804

From: Song Liu <hidden>
Date: 2021-08-10 05:11:02

Hi Mariusz,
On Aug 9, 2021, at 5:38 AM, Tkaczyk, Mariusz [off-list ref] wrote:

On 04.08.2021 23:50, Jens Axboe wrote:
quoted
On 8/4/21 3:47 PM, Song Liu wrote:
quoted
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

Re: [GIT PULL] md-fixes 20210804

From: Tkaczyk, Mariusz <hidden>
Date: 2021-08-10 09:47:04

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help