linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the md tree with the device-mapper tree
@ 2017-03-28  1:43 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2017-03-28  1:43 UTC (permalink / raw)
  To: Shaohua Li, Alasdair G Kergon, Mike Snitzer
  Cc: linux-next, linux-kernel, Heinz Mauelshagen, Artur Paszkiewicz

Hi Shaohua,

Today's linux-next merge of the md tree got a conflict in:

  drivers/md/raid5.h

between commit:

  78e470c26f52 ("md: add raid4/5/6 journal mode switching API")

from the device-mapper tree and commit:

  ff875738edd4 ("raid5: separate header for log functions")

from the md tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/md/raid5.h
index ec8ca15774d7,cdc7f92e1806..000000000000
--- a/drivers/md/raid5.h
+++ b/drivers/md/raid5.h
@@@ -775,35 -740,4 +750,5 @@@ extern struct stripe_head 
  raid5_get_active_stripe(struct r5conf *conf, sector_t sector,
  			int previous, int noblock, int noquiesce);
  extern int raid5_calc_degraded(struct r5conf *conf);
- extern int r5l_init_log(struct r5conf *conf, struct md_rdev *rdev);
- extern void r5l_exit_log(struct r5l_log *log);
- extern int r5l_write_stripe(struct r5l_log *log, struct stripe_head *head_sh);
- extern void r5l_write_stripe_run(struct r5l_log *log);
- extern void r5l_flush_stripe_to_raid(struct r5l_log *log);
- extern void r5l_stripe_write_finished(struct stripe_head *sh);
- extern int r5l_handle_flush_request(struct r5l_log *log, struct bio *bio);
- extern void r5l_quiesce(struct r5l_log *log, int state);
- extern bool r5l_log_disk_error(struct r5conf *conf);
- extern bool r5c_is_writeback(struct r5l_log *log);
- extern int
- r5c_try_caching_write(struct r5conf *conf, struct stripe_head *sh,
- 		      struct stripe_head_state *s, int disks);
- extern void
- r5c_finish_stripe_write_out(struct r5conf *conf, struct stripe_head *sh,
- 			    struct stripe_head_state *s);
- extern void r5c_release_extra_page(struct stripe_head *sh);
- extern void r5c_use_extra_page(struct stripe_head *sh);
- extern void r5l_wake_reclaim(struct r5l_log *log, sector_t space);
- extern void r5c_handle_cached_data_endio(struct r5conf *conf,
- 	struct stripe_head *sh, int disks, struct bio_list *return_bi);
- extern int r5c_cache_data(struct r5l_log *log, struct stripe_head *sh,
- 			  struct stripe_head_state *s);
- extern void r5c_make_stripe_write_out(struct stripe_head *sh);
- extern void r5c_flush_cache(struct r5conf *conf, int num);
- extern void r5c_check_stripe_cache_usage(struct r5conf *conf);
- extern void r5c_check_cached_full_stripe(struct r5conf *conf);
- extern struct md_sysfs_entry r5c_journal_mode;
- extern void r5c_update_on_rdev_error(struct mddev *mddev);
- extern bool r5c_big_stripe_cached(struct r5conf *conf, sector_t sect);
 +extern int r5c_journal_mode_set(struct mddev *mddev, int journal_mode);
  #endif

^ permalink raw reply	[flat|nested] 2+ messages in thread

* linux-next: manual merge of the md tree with the device-mapper tree
@ 2012-03-15  3:07 Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2012-03-15  3:07 UTC (permalink / raw)
  To: Neil Brown
  Cc: linux-next, linux-kernel, Jonathan E Brassow, Alasdair G Kergon

[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]

Hi Neil,

Today's linux-next merge of the md tree got a conflict in
drivers/md/dm-raid.c between commit 43390ddd7f36 ("The dm-raid code
currently fails to create a RAID array if any of the") from the
device-mapper tree and commit 760e35d7e573 ("md: tidy up rdev_for_each
usage") from the md tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/md/dm-raid.c
index f03e423,c5a875d..0000000
--- a/drivers/md/dm-raid.c
+++ b/drivers/md/dm-raid.c
@@@ -857,27 -855,11 +857,27 @@@ static int super_validate(struct mddev 
  static int analyse_superblocks(struct dm_target *ti, struct raid_set *rs)
  {
  	int ret;
 +	unsigned redundancy = 0;
 +	struct raid_dev *dev;
- 	struct md_rdev *rdev, *freshest, *tmp;
+ 	struct md_rdev *rdev, *freshest;
  	struct mddev *mddev = &rs->md;
  
 +	switch (rs->raid_type->level) {
 +	case 1:
 +		redundancy = rs->md.raid_disks - 1;
 +		break;
 +	case 4:
 +	case 5:
 +	case 6:
 +		redundancy = rs->raid_type->parity_devs;
 +		break;
 +	default:
 +		ti->error = "Unknown RAID type";
 +		return -EINVAL;
 +	}
 +
  	freshest = NULL;
- 	rdev_for_each(rdev, tmp, mddev) {
+ 	rdev_for_each(rdev, mddev) {
  		if (!rdev->meta_bdev)
  			continue;
  

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-03-28  1:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-28  1:43 linux-next: manual merge of the md tree with the device-mapper tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2012-03-15  3:07 Stephen Rothwell

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).