Re: [PATCH v3 1/2] usb: hso: fix error handling code of hso_create_net_device

[Dongliang Mu]

On Thu, Jul 22, 2021 at 3:24 PM Johan Hovold <johan@xxxxxxxxxx> wrote:
>
> On Thu, Jul 22, 2021 at 01:32:48PM +0800, Dongliang Mu wrote:
> > On Thu, Jul 22, 2021 at 12:42 AM Johan Hovold <johan@xxxxxxxxxx> wrote:
>
> > > > A version of this patch has already been applied to net-next.
> > >
> > > That was apparently net (not net-next).
> > >
> > > > No idea which version that was or why the second patch hasn't been
> > > > applied yet.
> >
> > It seems because I only sent the 1/2 patch in the v3. Also due to
> > this, gregkh asked me to resend the whole patchset again.
>
> Yeah, it's hard to keep track of submissions sometimes, especially if
> not updating the whole series.
>
> > > > Dongliang, if you're resending something here it should first be rebased
> > > > on linux-next (net-next).
> > >
> > > And the resend of v3 of both patches has now also been applied to
> > > net-next.
> > >
> > > Hopefully there are no conflicts between v2 and v3 but we'll see soon.
> >
> > You mean you apply a v2 patch into one tree? This thread already
> > contains the v3 patch, and there is no v2 patch in the mailing list
> > due to one incomplete email subject.
> >
> > BTW, v2->v3 only some label change due to naming style.
>
> Ok, I can't keep track of this either. I just noticed that this patch
> shows up in both net (for 5.14):
>
>         https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a6ecfb39ba9d7316057cea823b196b734f6b18ca
>
> and net-next (for 5.15):
>
>         https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=788e67f18d797abbd48a96143511261f4f3b4f21
>
> The net one was applied on the 15th and the net-next one yesterday.

I did not get any notification about this merge operation. So I cannot
help with this. Any chance to notify the developers the patch is
merged? In some subsystems, I will get notified by robots.

In the future, I will keep in mind updating the whole patch set. This
is easier for developers to follow.

>
> Judging from a quick look it appears to be the same diff so no damage
> done.

That's great.

>
> Johan