From: gregkh@linuxfoundation.org (Greg KH)
To: linus-amlogic@lists.infradead.org
Subject: patch "iio: adc: meson-saradc: use NULL instead of 0 for pointer" added to staging-testing
Date: Tue, 27 Jun 2017 08:43:54 +0200 [thread overview]
Message-ID: <20170627064354.GA29793@kroah.com> (raw)
In-Reply-To: <CAFBinCDOSaHF9GwGhMUpZjR7AUVWVwk7EJmHWt0q8bkChBhMZA@mail.gmail.com>
On Mon, Jun 26, 2017 at 08:57:18PM +0200, Martin Blumenstingl wrote:
> Hi Greg, Hi Jonathan,
>
> On Mon, Jun 26, 2017 at 7:09 AM, <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > iio: adc: meson-saradc: use NULL instead of 0 for pointer
> >
> > to my staging git tree which can be found at
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> > in the staging-testing branch.
> >
> > The patch will show up in the next release of the linux-next tree
> > (usually sometime within the next 24 hours during the week.)
> >
> > The patch will be merged to the staging-next branch sometime soon,
> > after it passes testing, and the merge window is open.
> >
> > If you have any questions about this process, please let me know.
> is there a way to drop below patch from your repo?
> during testing I found out that the code before and after this patch
> leads to a NULL deref. I provided a fix (see [0]) which solves the
> crash and the warning as reported by Paolo - and that fix is already
> part of v4.12-rc6
> so the patch below will cause a merge conflict
I already handled the merge conflict, can you verify I got it right in
my tree?
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-27 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14984537865458@kroah.com>
2017-06-26 18:57 ` patch "iio: adc: meson-saradc: use NULL instead of 0 for pointer" added to staging-testing Martin Blumenstingl
2017-06-26 19:30 ` Jonathan Cameron
2017-06-26 21:03 ` Martin Blumenstingl
2017-06-27 6:43 ` Greg KH [this message]
2017-06-28 20:12 ` Martin Blumenstingl
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=20170627064354.GA29793@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linus-amlogic@lists.infradead.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).