From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Greg KH <greg@kroah.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the staging.current tree
Date: Fri, 11 Oct 2019 21:36:10 +1100 [thread overview]
Message-ID: <20191011213610.5943cdea@canb.auug.org.au> (raw)
In-Reply-To: <20191011082902.GA1074099@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]
Hi Jonathan,
On Fri, 11 Oct 2019 10:29:02 +0200 Greg KH <greg@kroah.com> wrote:
>
> On Fri, Oct 11, 2019 at 08:10:23AM +0000, Jonathan Cameron wrote:
> > Hi Stephen
> >
> > Sorry, I've clearly let another one of these through.
> >
> > Stupid question of the day. Don't suppose you can share how you check these?
>
> There's a script, that I posted to the workflows mailing list, that
> should check these, based on Stephen's script.
>
> But it didn't seem to catch this problem, which is odd, I must have
> messed something up...
Attached is my script. It takes a range of commits to check. Usually
after I fetch a tree I pass it "^origin/master <old head of tree>...<new head of tree>".
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: check_fixes --]
[-- Type: application/x-shellscript, Size: 4344 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-11 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 20:42 linux-next: Fixes tag needs some work in the staging.current tree Stephen Rothwell
2019-10-11 8:10 ` Jonathan Cameron
2019-10-11 8:29 ` Greg KH
2019-10-11 10:36 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-28 13:01 Stephen Rothwell
2019-07-28 13:13 ` Greg KH
2019-07-29 8:24 ` Jonathan Cameron
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=20191011213610.5943cdea@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo@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).