linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Felipe Balbi <balbi@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the usb-gadget tree
Date: Thu, 16 Jan 2020 01:19:22 +0000	[thread overview]
Message-ID: <b7ef5047-c8c3-42cc-d049-fb72563d3544@linaro.org> (raw)
In-Reply-To: <20200116070726.7e2ef8cc@canb.auug.org.au>

On 15/01/2020 20:07, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    6a6ae4e8e926 ("usb: gadget: f_ncm: Use atomic_t to track in-flight request")
> 
> Fixes tag
> 
>    Fixes: 40d133d7f5426 ("usb: gadget: f_ncm: convert to new function interface

How should extra long fixes like this be divided up ?

Fixes: 40d133d7f542 ("usb: gadget: f_ncm: convert to new function 
interface with backward compatibility")


Fixes: 40d133d7f542 ("usb: gadget: f_ncm: convert to new function
                       interface with backward compatibility")

?

I don't see that for fixes like these.

Fixes: commit e9061c397839 ("nvmet: Remove the data_len field from the 
nvmet_req struct")


Fixes: 9e80635619b51 ("riscv: clear the instruction cache and all 
registers when booting")

---
bod



  reply	other threads:[~2020-01-16  1:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 20:07 linux-next: Fixes tag needs some work in the usb-gadget tree Stephen Rothwell
2020-01-16  1:19 ` Bryan O'Donoghue [this message]
2020-01-16  1:41   ` Stephen Rothwell
2020-01-16  1:45     ` Bryan O'Donoghue
2020-01-16  1:58       ` Stephen Rothwell
2020-01-16  2:08         ` Bryan O'Donoghue
2020-01-16  2:39           ` Stephen Rothwell
2020-01-16 13:07             ` Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2020-03-15 20:12 Stephen Rothwell
2019-05-03  5:31 Stephen Rothwell

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=b7ef5047-c8c3-42cc-d049-fb72563d3544@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=balbi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).