From: Luca Coelho <luca@coelho.fi>
To: Paul Menzel <pmenzel+linux-wireless@molgen.mpg.de>,
Kalle Valo <kvalo@codeaurora.org>
Cc: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
it+linux-wireless@molgen.mpg.de
Subject: Re: UBSAN: Undefined behaviour in drivers/net/wireless/intel/iwlwifi/mvm/utils.c:838:5
Date: Thu, 21 Dec 2017 12:57:07 +0200 [thread overview]
Message-ID: <1513853827.4827.504.camel@coelho.fi> (raw)
In-Reply-To: <4e18369a-4f39-3988-2072-5c7b9490b614@molgen.mpg.de>
On Thu, 2017-12-21 at 11:49 +0100, Paul Menzel wrote:
> Dear Kalle,
>
>
> On 12/21/17 11:38, Kalle Valo wrote:
> > Paul Menzel <pmenzel+linux-wireless@molgen.mpg.de> writes:
> >
> > > > http://pastebin.coelho.fi/7b624f474846da52.txt
> > >
> > > Thank you. The warning is gone now. Thank you. For the next time,
> > > it’d
> > > be great to provide the output of `git format-patch -1`, which
> > > can be
> > > applied with `git am`. The output of `git show` is with my
> > > knowledge
> > > hard to apply.
> >
> > 'patch -p1 < foo.patch' should work. Of course it omits the commit
> > log
> > but is usually enough for testing purposes.
>
> That’s what I did in the end. And then I have to do `git commit -a`
> to
> get the tree in a clean state.
>
> So `git format-patch -1` and uploading of that, for example with
> some
> CLI tool, for the win. ;-)
The choice here is: more work for me vs. more work for you. :) But I
guess I can easily do "git format-patch -1 --stdout" and pipe it to my
pastebin script...
--
Luca.
prev parent reply other threads:[~2017-12-21 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:25 Paul Menzel
2017-12-13 14:32 ` Luciano Coelho
2017-12-18 18:30 ` Luca Coelho
2017-12-20 11:00 ` Paul Menzel
2017-12-20 11:44 ` Luca Coelho
2017-12-21 10:38 ` Kalle Valo
2017-12-21 10:49 ` Paul Menzel
2017-12-21 10:57 ` Luca Coelho [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=1513853827.4827.504.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=it+linux-wireless@molgen.mpg.de \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=pmenzel+linux-wireless@molgen.mpg.de \
/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®