From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: linux-next: Fixes tag needs some work in the renesas tree
Date: Wed, 23 Jan 2019 10:41:20 +0000 [thread overview]
Message-ID: <TYXPR01MB1775F5B4C96D81299ECC3AF9C0990@TYXPR01MB1775.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190123103914.u7nlz624j5dmy7yr@verge.net.au>
Thank you Simon.
Fab
> From: Simon Horman <horms@verge.net.au>
> Sent: 23 January 2019 10:39
> Subject: Re: linux-next: Fixes tag needs some work in the renesas tree
>
> [CC linux-renesas-soc]
>
> On Wed, Jan 23, 2019 at 08:55:21AM +0000, Fabrizio Castro wrote:
> > > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > > Sent: 22 January 2019 20:56
> > > To: Simon Horman <horms@verge.net.au>
> > > Subject: linux-next: Fixes tag needs some work in the renesas tree
> > >
> > > Hi all,
> > >
> > > In commit
> > >
> > > 8d6e2bbaeceb ("arm64: dts: renesas: r8a774a1: Fix hsusb reg size")
> > >
> > > Fixes tag
> > >
> > > Fixes: ed898d4fc19d ("arm64: dts: renesas: r8a774a1: Add USB-DMAC and
> > >
> > > has these problem(s):
> > >
> > > - Subject has leading but no trailing parentheses
> > > - Subject has leading but no trailing quotes
> > >
> > > Please don't split Fixes tags across 2 lines.
> >
> > Hello Stephen,
> >
> > I am sorry for the trouble. My editor is configured to automatically wrap lines when they are too long, I'll be more careful next time.
> > Do you need me to do anything about this patch?
>
> Hi Fabrizio,
>
> I should have noticed this myself. I'll fix up the fixes tag
> in my next push. I don't think any action is needed by you
> at this time.
Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.
next prev parent reply other threads:[~2019-01-23 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:56 linux-next: Fixes tag needs some work in the renesas tree Stephen Rothwell
2019-01-23 8:55 ` Fabrizio Castro
2019-01-23 10:39 ` Simon Horman
2019-01-23 10:41 ` Fabrizio Castro [this message]
2019-01-23 12:21 ` 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=TYXPR01MB1775F5B4C96D81299ECC3AF9C0990@TYXPR01MB1775.jpnprd01.prod.outlook.com \
--to=fabrizio.castro@bp.renesas.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-renesas-soc@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).