On Wed, 1 Aug 2018 11:21:13 -0700
Nick Desaulniers wrote:
> On Tue, Jul 31, 2018 at 10:41 PM Martin Schwidefsky
> wrote:
> >
> > On Tue, 31 Jul 2018 16:09:06 -0700
> > Nick Desaulniers wrote:
> >
> > > + More maintainers and lists for visibility
> > >
> > > On Tue, Jul 31, 2018 at 3:32 PM Nic
On Tue, Jul 31, 2018 at 10:41 PM Martin Schwidefsky
wrote:
>
> On Tue, 31 Jul 2018 16:09:06 -0700
> Nick Desaulniers wrote:
>
> > + More maintainers and lists for visibility
> >
> > On Tue, Jul 31, 2018 at 3:32 PM Nick Desaulniers
> > wrote:
> > >
> > > I'm currently looking into cleaning up the
On Tue, 31 Jul 2018 16:09:06 -0700
Nick Desaulniers wrote:
> + More maintainers and lists for visibility
>
> On Tue, Jul 31, 2018 at 3:32 PM Nick Desaulniers
> wrote:
> >
> > I'm currently looking into cleaning up the code duplication between
> > current_text_addr() and _THIS_IP_, virtually eve
On 07/31/2018 04:09 PM, Nick Desaulniers wrote:
> + More maintainers and lists for visibility
>
Ideally the linux-a...@vger.kernel.org mailing list would be sufficient,
but I doubt that it is. :(
--
~Randy
+ More maintainers and lists for visibility
On Tue, Jul 31, 2018 at 3:32 PM Nick Desaulniers
wrote:
>
> I'm currently looking into cleaning up the code duplication between
> current_text_addr() and _THIS_IP_, virtually every implementation of
> current_text_addr() and _THIS_IP_ itself are basical
I'm currently looking into cleaning up the code duplication between
current_text_addr() and _THIS_IP_, virtually every implementation of
current_text_addr() and _THIS_IP_ itself are basically:
#define _THIS_IP_ ({ __label__ _l; _l: &&_l; })
For a few arch's, they have inline assembly instead (for
6 matches
Mail list logo