All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	richard.laing@alliedtelesis.co.nz, linux-arm-msm@vger.kernel.org
Subject: Re: [RESEND] Conflict between char-misc and netdev
Date: Thu, 12 Aug 2021 19:35:18 +0530	[thread overview]
Message-ID: <20210812140518.GC7897@workstation> (raw)
In-Reply-To: <20210812065113.04cc1a66@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Thu, Aug 12, 2021 at 06:51:13AM -0700, Jakub Kicinski wrote:
> On Thu, 12 Aug 2021 19:02:15 +0530 Manivannan Sadhasivam wrote:
> > Due to the below commit in netdev there is a conflict between char-misc
> > and netdev trees:
> > 
> > 5c2c85315948 ("bus: mhi: pci-generic: configurable network interface MRU")
> > 
> > Jakub, I noticed that you fixed the conflict locally in netdev:
> > 
> > d2e11fd2b7fc ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net")
> > 
> > But the commit touches the MHI bus and it should've been merged into mhi
> > tree then it goes via char-misc. It was unfortunate that neither
> > linux-arm-msm nor me were CCed to the patch :/
> > 
> > Could you please revert the commit?
> 
> Apologies for missing the lacking CC list, the extra resolution work,
> etc. etc. Let me try to sharpen the "were maintainers CCed" check in
> patchwork to make this less likely in the future.
> 

No worries. I know how loaded the netdev list is :)

> About the situation at hand - is the commit buggy? Or is there work
> that's pending in char-misc that's going to conflict in a major way? 
> Any chance you could just merge the same patch into mhi and git will 
> do its magic?

I'm not happy with the MHI change and I do have a comment about the
variable "mru_default". So it'd be good if we revert the commit
entirely!

Also I do have few more patches coming for the same driver touched by
5c2c85315948.

Thanks,
Mani

  reply	other threads:[~2021-08-12 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 13:32 [RESEND] Conflict between char-misc and netdev Manivannan Sadhasivam
2021-08-12 13:51 ` Jakub Kicinski
2021-08-12 14:05   ` Manivannan Sadhasivam [this message]
2021-08-12 16:12     ` Jakub Kicinski
2021-08-13  3:56       ` Richard Laing

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=20210812140518.GC7897@workstation \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard.laing@alliedtelesis.co.nz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.