From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Hariprasad Kelam <hariprasad.kelam@gmail.com>,
mingo@redhat.com, David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] trace: events: fix error directive in argument list
Date: Sat, 30 Mar 2019 06:50:38 -0700 [thread overview]
Message-ID: <CAJieiUgLUV=z-OSJdevVpKsdUB3PvWRtwueqf0o7oGMX2VLMiw@mail.gmail.com> (raw)
In-Reply-To: <20190330084016.24f8ad46@gandalf.local.home>
On Sat, Mar 30, 2019 at 5:40 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sat, 30 Mar 2019 13:01:41 +0100
> Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote:
>
> > OK, I see. IMO, it would be better to have 2 patches for this:
> > one for the redundant assignment to pin6 and anotther one for
> > the IS_ENABLED() change but feel free, if needed, to add my
>
> I agree with it being separate patches. I'm big on the "one patch
> accomplishes one task" ideology.
>
yes, I will take care of the pin6 assignment separately. This patch
can only address the sparse error.
prev parent reply other threads:[~2019-03-30 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 19:53 Hariprasad Kelam
2019-03-25 20:11 ` Steven Rostedt
2019-03-27 0:20 ` Roopa Prabhu
2019-03-27 0:19 ` Roopa Prabhu
2019-03-27 15:53 ` Steven Rostedt
2019-03-29 23:12 ` Luc Van Oostenryck
2019-03-29 23:22 ` Luc Van Oostenryck
2019-03-30 11:07 ` Hariprasad Kelam
2019-03-30 12:01 ` Luc Van Oostenryck
2019-03-30 12:40 ` Steven Rostedt
2019-03-30 13:50 ` Roopa Prabhu [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='CAJieiUgLUV=z-OSJdevVpKsdUB3PvWRtwueqf0o7oGMX2VLMiw@mail.gmail.com' \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=hariprasad.kelam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®