linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ayush Sawal <ayush.sawal@chelsio.com>
Cc: David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	ayush.sawal@asicdesigners.com,
	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 net-next tree
Date: Tue, 2 Jun 2020 20:18:21 +1000	[thread overview]
Message-ID: <20200602201821.615b9b7b@canb.auug.org.au> (raw)
In-Reply-To: <8a8bc5f4-2dc3-5e2c-3013-51954004594c@chelsio.com>

[-- Attachment #1: Type: text/plain, Size: 687 bytes --]

Hi Ayush,

On Tue, 2 Jun 2020 13:01:09 +0530 Ayush Sawal <ayush.sawal@chelsio.com> wrote:
>
> On 6/2/2020 4:42 AM, Stephen Rothwell wrote:
> >
> > In commit
> >
> >    055be6865dea ("Crypto/chcr: Fixes a coccinile check error")
> >
> > Fixes tag
> >
> >    Fixes: 567be3a5d227 ("crypto:
> >
> > has these problem(s):
> >
> >    - Subject has leading but no trailing parentheses
> >    - Subject has leading but no trailing quotes
> >
> > Please do not split Fixes tags over more than one line.  
> 
> I am so sorry for this mistake.
> Is there a way to fix this?

No, David does not rebase his tree.  Just remember for next time.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-06-02 10:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 23:12 linux-next: Fixes tag needs some work in the net-next tree Stephen Rothwell
2020-06-02  7:31 ` Ayush Sawal
2020-06-02 10:18   ` Stephen Rothwell [this message]
2020-06-02 10:30     ` Ayush Sawal
  -- strict thread matches above, loose matches on Subject: below --
2021-09-26 21:37 Stephen Rothwell
2021-08-16 22:04 Stephen Rothwell
2021-08-17  7:53 ` Nikolay Aleksandrov
2021-04-18 21:53 Stephen Rothwell
2021-03-30  1:15 Stephen Rothwell
2021-03-26 23:03 Stephen Rothwell
2020-09-15 23:04 Stephen Rothwell
2020-04-22 22:16 Stephen Rothwell
2020-02-27  4:42 Stephen Rothwell
2020-02-27  9:01 ` Maxim Mikityanskiy
2020-02-17  4:23 Stephen Rothwell
2019-12-18  6:35 Stephen Rothwell
2019-11-04 21:01 Stephen Rothwell
2019-09-10 14:37 Stephen Rothwell
2019-08-01 22:54 Stephen Rothwell
2019-07-29 21:25 Stephen Rothwell
2019-07-22 21:35 Stephen Rothwell
     [not found] ` <CANP3RGcqGrPnt9eOiAKRbxWVuBkRHRQdWPnANKwrYvtVnTqaSQ@mail.gmail.com>
2019-07-23  0:49   ` Stephen Rothwell
2019-07-03 21:42 Stephen Rothwell
2019-06-30 21:37 Stephen Rothwell
2019-04-22 21:26 Stephen Rothwell
2019-04-23 12:19 ` John Hurley
2019-04-05  5:58 Stephen Rothwell
2019-03-21 18:54 Stephen Rothwell
2019-02-25  8:00 Stephen Rothwell
2019-02-27  1:12 ` tanhuazhong
2019-02-27  2:23   ` Stephen Rothwell
2019-02-27  3:16     ` tanhuazhong
2019-02-19 22:31 Stephen Rothwell
2019-02-20  4:40 ` Vinod Koul
2019-02-20  5:38   ` Stephen Rothwell
2019-02-20  6:48   ` David Miller
2019-02-20  8:36     ` Jiri Pirko
2019-02-20 19:02       ` David Miller
2019-02-20 19:58         ` Jiri Pirko
2019-02-20 20:25           ` David Miller
2019-02-20 20:26             ` Jiri Pirko
2019-02-20 19:59         ` Stefano Brivio
2019-02-20 20:25           ` David Miller
2019-02-20 20:37             ` Stefano Brivio
2019-02-20 20:42               ` David Miller
2019-02-21  5:34           ` Vinod Koul
2019-02-11 22:17 Stephen Rothwell
2019-01-31 20:35 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=20200602201821.615b9b7b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ayush.sawal@asicdesigners.com \
    --cc=ayush.sawal@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).