linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <jejb@linux.vnet.ibm.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Rebasing the for-next branch
Date: Tue, 16 Nov 2021 15:24:45 -0800	[thread overview]
Message-ID: <652bab99-7c52-7378-792f-6b814671c0eb@acm.org> (raw)

Hi Martin,

Do you plan to rebase the for-next branch of 
git://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git on v5.16-rc1? 
I just noticed that there are multiple merge conflicts between the UFS 
patch series I'm working on (based on mkp-scsi/for-next) and v5.16-rc1. 
Although rebasing is being frowned upon in the Linux kernel community, 
Linus probably will be grateful if we do the work of reducing merge 
conflicts before the v5.17-rc1 pull request is sent.

Thanks,

Bart.

             reply	other threads:[~2021-11-16 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 23:24 Bart Van Assche [this message]
2021-11-16 23:34 ` Rebasing the for-next branch Martin K. Petersen

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=652bab99-7c52-7378-792f-6b814671c0eb@acm.org \
    --to=bvanassche@acm.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).