From: "George G. Davis" <george_davis@mentor.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: sysctl: cleanup net_sysctl_init error exit paths
Date: Mon, 8 Jul 2019 18:47:32 -0400 [thread overview]
Message-ID: <20190708224732.GA8009@mam-gdavis-lt> (raw)
In-Reply-To: <20190517144345.GA16926@mam-gdavis-lt>
Hello David,
On Fri, May 17, 2019 at 10:43:45AM -0400, George G. Davis wrote:
> Hello David,
>
> On Thu, May 16, 2019 at 02:27:44PM -0700, David Miller wrote:
> > From: "George G. Davis" <george_davis@mentor.com>
> > Date: Thu, 16 May 2019 11:23:08 -0400
> >
> > > Unwind net_sysctl_init error exit goto spaghetti code
> > >
> > > Suggested-by: Joshua Frkuska <joshua_frkuska@mentor.com>
> > > Signed-off-by: George G. Davis <george_davis@mentor.com>
> >
> > Cleanups are not appropriate until the net-next tree opens back up.
> >
> > So please resubmit at that time.
>
> I fear that I may be distracted by other shiny objects by then but
> I'll make a reminder and try to resubmit during the next merge window.
Since the "Linux 5.2" kernel has been released [1], I'm guessing that the
net-next merge window is open now? If yes, the patch remains unchanged
since my initial post. Please consider applying or let me know when to
resubmit when the net-next merge window is again open.
TIA!
>
> Thanks!
>
> >
> > Thank you.
>
> --
> Regards,
> George
--
Regards,
George
[1] https://lwn.net/Articles/792995/
next prev parent reply other threads:[~2019-07-08 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 15:23 [PATCH] net: sysctl: cleanup net_sysctl_init error exit paths George G. Davis
2019-05-16 21:27 ` David Miller
2019-05-17 14:43 ` George G. Davis
2019-07-08 22:47 ` George G. Davis [this message]
2019-09-17 15:53 ` George G. Davis
2019-09-18 9:44 ` Nicolas Dichtel
2019-09-18 15:00 ` George G. Davis
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=20190708224732.GA8009@mam-gdavis-lt \
--to=george_davis@mentor.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@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).