From: Greg KH <gregkh@linuxfoundation.org>
To: Kay Sievers <kay@vrfy.org>
Cc: Jan Beulich <JBeulich@suse.com>,
yuanhan.liu@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] syslog: fill buffer with more than a single message for SYSLOG_ACTION_READ
Date: Tue, 26 Jun 2012 12:55:11 -0700 [thread overview]
Message-ID: <20120626195511.GA2959@kroah.com> (raw)
In-Reply-To: <CAPXgP10iHmADRGQ8TvmWG3-LB7PhoVFcRTF7PDPq29CWQNu65w@mail.gmail.com>
On Tue, Jun 26, 2012 at 02:34:49AM +0200, Kay Sievers wrote:
> On Tue, Jun 26, 2012 at 2:01 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Mon, Jun 25, 2012 at 09:35:03PM +0200, Kay Sievers wrote:
> >> On Mon, Jun 25, 2012 at 9:20 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >>
> >> > Ok, so I'm confused, you want me to apply this patch and then revert a
> >> > different one? Which one, 4a77a5a06ec66ed05199b301e7c25f42f979afdc?
> >>
> >> b56a39ac conflicts and is replaced with that patch.
> >> 4a77a5a0 should stay, as it fixes an actual problem, even with the old
> >> code, I think.
> >
> > Ok, I'm even more confused now. Maybe I just need more coffee.
> >
> > Can you list what exactly I should do here? Should I apply this patch?
> > Revert some other patch? Which one(s)?
>
> Revert b56a39ac (return -EINVAL) and apply the patch from Jan. The
> problem b56a39ac solved , is replaced by other logic in Jan's patch.
Ok, now done, there's nothing else needed here, right?
thanks,
greg k-h
next prev parent reply other threads:[~2012-06-26 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 15:36 [PATCH] syslog: fill buffer with more than a single message for SYSLOG_ACTION_READ Jan Beulich
2012-06-23 18:03 ` Kay Sievers
2012-06-25 7:05 ` Jan Beulich
2012-06-25 19:20 ` Greg KH
2012-06-25 19:35 ` Kay Sievers
2012-06-26 0:01 ` Greg KH
2012-06-26 0:34 ` Kay Sievers
2012-06-26 19:55 ` Greg KH [this message]
2012-06-27 7:15 ` Jan Beulich
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=20120626195511.GA2959@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=JBeulich@suse.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuanhan.liu@linux.intel.com \
/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