From: Rich Felker <dalias@libc.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Rob Landley <rob@landley.net>,
linux-sh@vger.kernel.org,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-kernel@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] sh: fix syscall tracing
Date: Fri, 18 Sep 2020 15:29:42 -0400 [thread overview]
Message-ID: <20200918192942.GA3265@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200916002843.GR3265@brightrain.aerifal.cx>
On Tue, Sep 15, 2020 at 08:28:45PM -0400, Rich Felker wrote:
> On Tue, Sep 15, 2020 at 12:35:28PM +0200, John Paul Adrian Glaubitz wrote:
> > Hi Rich!
> >
> > On 9/10/20 3:37 PM, Rich Felker wrote:
> > >> Which I reported to Rich on the 2nd and he had me test a one line patch fixing
> > >> it (adding an extra #include) on the 3rd, but I just did a fresh pull and the
> > >> j2_defconfig build still broke a week later.
> > >
> > > Yes, that's presently the other regression fix I have queued for the
> > > second pull request.
> >
> > Any news on this? Seems like Linus just tagged -rc5 this week.
>
> I rebased against -rc5 and pushed for-next a couple days ago. It
> doesn't look like there are any problems so I'll proceed with the PR.
It's now been merged.
prev parent reply other threads:[~2020-09-18 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 5:48 Rich Felker
2020-09-03 8:13 ` John Paul Adrian Glaubitz
2020-09-03 10:14 ` John Paul Adrian Glaubitz
2020-09-03 16:16 ` Rich Felker
2020-09-07 9:52 ` John Paul Adrian Glaubitz
2020-09-07 17:44 ` Rich Felker
2020-09-10 9:55 ` John Paul Adrian Glaubitz
2020-09-10 11:02 ` Rob Landley
2020-09-10 13:37 ` Rich Felker
2020-09-15 10:35 ` John Paul Adrian Glaubitz
2020-09-16 0:28 ` Rich Felker
2020-09-18 19:29 ` Rich Felker [this message]
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=20200918192942.GA3265@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®