On Mon, Feb 04, 2019 at 10:22:16AM +0100, Johan Hovold wrote:
> On Mon, Feb 04, 2019 at 01:04:37AM -0800, Myungho Jung wrote:
> > On Sun, Feb 03, 2019 at 11:29:00PM -0800, Myungho Jung wrote:
> > > On Sun, Feb 03, 2019 at 11:53:23AM +0100, Johan Hovold wrote:
>
> > > > You should add a Fixes tag identifying the commit which introduced each
> > > > bug and a stable-cc tag. If you want you can indicate the version after
> > > > a # sign, but that can also be inferred from the fixes tag.
> > > >
> > > > For the hci_ldisc fix I think the tags would be:
> > > >
> > > > Fixes: 2a973dfada2b ("Bluetooth: hci_uart: Add new line discipline enhancements")
> > > > Cc: stable <stable@xxxxxxxxxxxxxxx> # 4.2
> > > >
> > > > You can use git blame to track down the offending commits.
> > > >
> > > > This should all be explained here:
> > > >
> > > > https://www.kernel.org/doc/html/latest/process/submitting-patches.html
>
> > I have one more question. The title of new patches should be version 3 like
> > this?
> > [PATCH v3] Bluetooth: hci_ath: ...
> > [PATCH v3] Bluetooth: hci_ldisc: ...
> >
> > Or newly start with [PATCH]?
>
> You should keep and increment the revision number even if you split a
> patch (so use v3 for the resend).
>
> I suggest you send both patches in a series (as they are related); take
> a look at git-send-email for a convenient way to do that.
>
> And always include a brief changelog (below the cut-off line, "---")
> when revising patches.
>
> Johan
I see. I'll submit version 3 as a patchset with change logs.
Thanks,
Myungho
